I host a website on one of my own machines, but when I view the pages from work (everywhere else is OK), sometimes I just see the raw HTML rather than the rendered webpage. Anyone have any ideas as to what's going on?
Don't know how much time you want/ need to put into this, but can you bypass the proxy in anyway? If not locally, then configure apache to listen to another port?
(I would have added this as an edit but it doesn't seem to work! :))
Don't know how much time you want/ need to put into this, but can you bypass the proxy in anyway? If not locally, then configure apache to listen to another port?
(I would have added this as an edit but it doesn't seem to work! :))
It's one of those transparent proxies built into the router, IIRC. It's not really too much of a problem, so long as it's just a local issue.
Looks to be a problem with the company's Squid WWW cache setting the content type to be text/plain every now and then, even though my webserver sets the content type to text/html.
It displays correctly (or so I think) in my browser.
I've had a look at the code of the page. It hasn't any HTML header, just a couple of IMG tags and some text; it looks like a fragment of the BODY part of a page.
Maybe that's the problem: since the HTML header is missing, some browsers think that it's a text file. Just an idea.
It displays correctly (or so I think) in my browser.
I've had a look at the code of the page. It hasn't any HTML header, just a couple of IMG tags and some text; it looks like a fragment of the BODY part of a page.
Maybe that's the problem: since the HTML header is missing, some browsers think that it's a text file. Just an idea.
Everything is treated as being within a HTML tag by default if there isn't one already. The content-type (set in the HTTP header) tells the browser what sort of document it is. Besides, if it was misidentified as a plain text document, it would do that every time it's loaded.
Comments
No :) But have you tried different browsers at work? Different machines on the same work network?
Are you able to give out the URL, a few of us could test and report back the results, maybe we can spot a pattern?
I've a feeling the company's web proxy is doing something odd as multiple (Linux) web browsers show the same problem.
(I would have added this as an edit but it doesn't seem to work! :))
It's one of those transparent proxies built into the router, IIRC. It's not really too much of a problem, so long as it's just a local issue.
Nah, those are big files!
I've had a look at the code of the page. It hasn't any HTML header, just a couple of IMG tags and some text; it looks like a fragment of the BODY part of a page.
Maybe that's the problem: since the HTML header is missing, some browsers think that it's a text file. Just an idea.
Everything is treated as being within a HTML tag by default if there isn't one already. The content-type (set in the HTTP header) tells the browser what sort of document it is. Besides, if it was misidentified as a plain text document, it would do that every time it's loaded.