Jerry, thanks for the detailed analysis... sure sounds like you've hit the nail on the head.
When we 'tag' .34 - we won't be rolling it. I will personally be looking at this quirk in the next day or two, and so may others. If a patch is prepared that 'fits' [increases stability - doesn't restructure a ton of code] then we will 'roll it in' to .34. Agreed that this isn't nice behavior, but also recognize that this is one bug in many, and many are now fixed and many others may yet be unspotted. We want to get something into folks hands, even if it is only 'alpha' quality. Release early, release often assures that many more bugs are fixed much more quickly. Bill At 01:00 PM 3/26/2002, you wrote: >Jerry Baker wrote: > > > > I just noticed something about this problem. If you request > > /nonexistentfile.html then the error response is sent back with > > text/html, but if you request /nonexistentfile then it still comes back > > as text/plain. > > > > -- > > Jerry Baker > >Not only that. If you request /nonexistentfile.exe, it gets sent back as >application/octet-stream. The ErrorDocument is being returned with >whatever content-type matches the file extension of the requested >document. I doubt many people want to download the ErrorDocument in the >case that they request a non-existent application/octet-stream URI. > >-- >Jerry Baker
