Sometimes it seems like the content type is text/plain. What I mean is that all HTML for the page shows up as if I was viewing the source. Reloading the page has no effect.

I'm not able to force this to happen, it appears to be a quasi-random thing based on phase of the moon and tide levels. However, I remember it's happened in both Konquerer and Netscape, so I assume it's not a browser thing.

Can anyone shed some light on this? I've not noticed the symptoms with any other web site, so I'm hoping the problem isn't on my end. (Then I would look foolish)

Replies are listed 'Best First'.
Re: Mysterious Perlmonks Page Display
by mdillon (Priest) on Jul 25, 2001 at 03:36 UTC

    this sounds like the typical difference shown between IE and Netscape when viewing text/plain files. for some reason, IE ignores the content-type and shows many text/plain pages as if they are text/html. combined with what tye said, i would guess that a transparent proxy is caching, but is not sending it out with the original MIME type (using text/plain instead since the extension is .pl, not .html). IE's erroneous behavior makes it seem like nothing is wrong, whereas Netscape and Konqueror are both acting correctly on the text/plain MIME type.

    if you have LWP installed, use the HEAD program to fetch the HTTP headers for the page in question to be sure.

      You folks will never cease to amaze me! Well, there's one less mystery in the world now. Your explanations were spot on.

      Thanks and Praise!
Re: Mysterious Perlmonks Page Display
by Hero Zzyzzx (Curate) on Jul 24, 2001 at 21:58 UTC

    That has never happened to me in the multitude of browsers and OSs I use to access

    The list
    • Linux
      • Konqueror
      • Netscape
      • Opera
      • Mozilla
      • lynx,links, and w3m
    • Win32
      • IE
      • Netscape
      • Opera
      • Mozilla

    I'm kind of a browser junkie, and test all my pages in nearly everything I can. Sorry!

      If Hero Zzyzzx has failed to see this on so many browsers but Superlman has seen it on more than one, I'd suspect something outside the browser but somewhat specific to Superlman. My first guess is a web proxy.

      Some ISPs set up transparent web proxies (usually for caching) that don't require the browser to know that a proxy is being used. So Superlman's web traffic might be going through a proxy w/o Superlman knowing this and no software is bug free, including web proxies.

      I had an ISP whose proxy would cache incomplete pages if I hit my browser's "Stop" button during the first load of the page (making it very hard to get the complete page later). Anyway, that is something that might be worth checking into.

              - tye (but my friends call me "Tye")