Useful Links

**Janet H** · 01-29-2011, 04:53 PM

That can happen sometimes when a transmission is interrupted between server and user but as you report no trouble in other browsers it's hard to pin point.

One thing you might try is uninstalling FF and reloading.

TromboneAl · 01-29-2011, 05:34 PM

Thanks. The isp has been flakey today. Service has been interrupted several times. I'll experiment more later.

Post from ipod.

TromboneAl · 01-29-2011, 05:54 PM

Tried safe mode -- same thing.

When I run with private browsing, it will work fine between 0 and 3 times. That is, sometimes it fails the first time, sometimes I can do it about 3 times and have it work each time.

But once it fails, it will no longer work (e.g. I can try 10 times and it fails each time).

I'll give it some time (maybe ISP will fix something), then try some more stuff. I use that button a lot.

With IE, I did it 10 times with no failures. My understanding is that IE handles file types differently -- this may or may not be relevant:

When you click on a link, your browser sends an http request. The system at the other end evaluates the request, then sends back an http response header attached to the return file. NOTE: this is in addition to any statements included in the <head> section of an actual html document.

Browsers handle the reception of the response header transparently so the general user is not aware of it.

One of the functions of the http response header is to define what type of file is attached, via a "content-type" (often referred to as MIME type) declaration - this tells the browser how to handle the file. It is this content-type in the response header (NOT the filename extension) that FFox uses to determine how to handle the file. It is the responsibility of the server housing the files to send an appropriate content-type in the http response header.

Sometimes the server housing the file in question may not be configured correctly and delivers an http response header with an incorrect content type. Files to be displayed as Html should have content type of "text/html"; plain text files should have content type of "text/plain"; executable files will have content type "application/octet-stream" or one more specific to the application.

If a file is served with a content type that isn't automatically displayed or handled by FFox, it will ask you what to do with the file. MSIE, on the other hand, ignores the http standards, ignores the http header content-type, and takes its own best guess on how to handle the file - consequently many server admins aren't even aware of the problem if they are serving the files with the wrong content type.

So if your file is being served with a content type other than "text/html" then TBird won't display it as a web page.

You can see what content type was received by FFox. Right-click on an empty part of the displayed page and choose "View Page Info" from the resulting menu. Under the General tab, look at the "type" line.

If you're not convinced (or don't trust what FFox tells you, or, as in your case, if the page isn't displayed by FFox at all so you can't view its page info), go to www.web-sniffer.net and enter the URL of your page or link. Then scroll down to the reply header that is displayed and see what is listed as "content type".

If an inappropriate content type is being sent, contact the webmaster, as they need to fix this at the server.

Sue J · 01-29-2011, 06:40 PM

Quote:

Originally Posted by TromboneAl

Time Zone Pacific Standard Time
Total Physical Memory 2,560.00 MB
Available Physical Memory 1.61 GB
Manhood length 12 inches
Total Virtual Memory 2.00 GB
Available Virtual Memory 1.96 GB

That's quite a default setting you've got there, Al.

Nords · 01-30-2011, 11:18 AM

Quote:

Originally Posted by TromboneAl

OS Name Microsoft Windows XP Professional
Manhood length 12 inches

I can't choose between the punchlines:
"At least that's what Microsoft claims 12 inches looks like"
or
"It'll run better on a Mac!"

**Janet H** · 01-30-2011, 11:57 AM

Quote:

Originally Posted by Nords

I can't choose between the punchlines:
"At least that's what Microsoft claims 12 inches looks like"
or
"It'll run better on a Mac!"

Not touching that one with a ten foot pole ... arh, arh, etc

TromboneAl · 01-31-2011, 08:21 AM

So I'm apparently the only one who gets this PHP problem, and this is the only VBulletin forum for which it happens for me.

REWahoo · 01-31-2011, 08:29 AM

Quote:

Originally Posted by TromboneAl

So I'm apparently the only one who gets this PHP problem, and this is the only VBulletin forum for which it happens for me.

It would appear that way.

TromboneAl · 01-31-2011, 08:37 AM

My guess is that there is some small problem with this forum software, but that it only manifests itself due to some problem with my computer or, more likely, ISP. Instead of uninstalling and reinstalling etc., I'm going to give it a week to fix itself.

BigNick · 01-31-2011, 08:52 AM

If a URL ending in .PHP is proposing a file download, there is something wrong on the server.

Can you save the file and upload some or part of it here?

TromboneAl · 01-31-2011, 11:09 AM

Thanks for the help. Here is the html file to which the "Newest Post" button points (with text in the middle removed because it was too big to upload as an attachment), and the php file itself.

TromboneAl · 01-31-2011, 11:31 AM

I just tried this from Lena's computer, and the same problem exists. That rules out any issues on my computer.

I called my ISP and they say there are no issues on their end, although they are generally clueless. I had them reset my modem, and the problem is still present.

BigNick · 01-31-2011, 12:38 PM

OK, so at least it isn't serving you up the full PHP source file. That's a relief. Apart from that, my IP-fu isn't up to diagnosing the exact nature of the problem.

TromboneAl · 01-31-2011, 05:43 PM

It's working now!

I tried it 10 times in a row, and it worked every time. I made no changes since the last time it failed, so something changed on the ISP side or in the forum software (?)

In any case, this shows that sometimes trying too hard to fix something is counter-productive. If I'd just waited four days, I would have saved myself a lot of bother.

ls99 · 01-31-2011, 07:01 PM

See, the government method works. Ignore the problem long enough, either the problem goes away, or by some magic it is repaired.

Edit add: You would not make a good gummint worker, tried too hard for too long.

Nords · 01-31-2011, 07:05 PM

Quote:

Originally Posted by TromboneAl

I made no changes since the last time it failed, so something changed on the ISP side or in the forum software (?)
In any case, this shows that sometimes trying too hard to fix something is counter-productive. If I'd just waited four days, I would have saved myself a lot of bother.

You'd have to waterboard the ISP to get them to admit that they rebooted their servers... "Oh, yeah, we do that every Sunday night"...

Useful Links

Latest Threads

Social Knowledge Community

About Us