Re: Back -> raw HTML

Sorry, I know there's candy hidden somewhere and I'm already salivating! I
must attempt to continue on this thread. [Though you may wish not to ...
that's OK]

[I'm digest so if it's already solved ... excuse please]

[I'm way over par on the lingo ... excuse please]

Someone pick these thoughts to pieces ...

1. The browser in question when it makes the original request of the server
receives back information around the html file which is different than what
it receives from a back button request.

2. The environment passed from the browser to the server could be different
amongst Back Button, Back Link [based on HTTP_REFERER], and the original
request.

3. Info in a cookie may have been changed on the first request.

4. The process that builds the page may latch onto these differences and do
something different [like leave out the incorrect mime type header].

5. The environment around the html when it is delivered the first time is
not present in the same way if the file is pulled up from a local cache.




John

HWG: hwg-servers mailing list archives, maintained by Webmasters @ IWA