in reply to RE: reading binary files in windows
in thread reading binary files in windows

A redirect implies that the URL they requested does have valid content. If you're returning something to the browser in a 404 status, it makes sense not to cache it, since a) there is no "url" associated with the content (we have to let the browser know it's a bad url, right? 404!) and b) what happens when content appears at this URL? Do we really want to cache a '404' mesage?

Many browsers also disregard the content to pages delivered in 404 status, opting for their own simple message instead.

  • Comment on RE: RE: reading binary files in windows

Replies are listed 'Best First'.
RE: RE: RE: reading binary files in windows
by JackHammer (Acolyte) on Oct 27, 2000 at 22:54 UTC
    But by writing my own handler it doesn't show up as a 404. This is a "temporary" solution to a problem on a site that just rolled out with 6000+ products that have about 30 images each... Any image that is requested under a product directory with a certain name I display a certain "art is missing" image. It's just an interum solution till they art department can catch up.
[reply]
      If you're putting valid content at a URL via a 404 handler, just be sure your script prints out a "Status: 200 OK" header to override the server's 404 status message so that it appears normally. This has the added benefit of allowing search engines to pick up the page, where they would discard it otherwise with a 404 message.
[reply]
[d/l]

In Section Seekers of Perl Wisdom