On Mon, 27 Jan 2003, Matthias Englert wrote: > What do you mean by doesn't work? What happens? Have you checked > the header with wget or > You can - and you have to - return a nice page even if you trigger > a 404 header. :-)
Look closely at the title bar on your web browser when you visit http://stevesobol.com:8001/nf.php - it's a midgard site but that particular page is served off the filesystem. Source code: header("Status: HTTP/1.0 404 Not Found"); echo "testing"; Now, if the web browser gets a 404 back from a client, if it's Netscape or IE, it'll normally print "404 Not Found" in the titlebar. Notice that that's not happening here. Lynx also would print a 404 Not Found status down at the bottom of the screen if a visit to a page generated a 404, and that doesn't happen on this page. wget also grabs a copy of the page, instead of complaining about the page not being found. I think at the point that my code gets executed, the web server has already sent back a status code 200/OK to the browser, and that's why the browser isn't interpreting my 404 as a 404. -- Steve Sobol, CTO JustThe.net LLC, Mentor On The Lake, OH http://JustTheNetLLC.com/ 888.480.4NET (4638) A practicing member of the Geek Orthodox religion! --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
