Hi Mike, I agree that it would be strange for the browser to insert the extra markup, but IE likes to use it's own error messages so just wanted to rule out that possibility.
According to the W3C <http://www.w3.org/Protocols/rfc2616/rfc2616- sec10.html>: ----------------- 10.4.4 403 Forbidden The server understood the request, but is refusing to fulfill it. Authorization will not help and the request SHOULD NOT be repeated. If the request method was not HEAD and the server wishes to make public why the request has not been fulfilled, it SHOULD describe the reason for the refusal in the entity. If the server does not wish to make this information available to the client, the status code 404 (Not Found) can be used instead. ----------------- So perhaps CGI.pm is taking the steps to describe the reason. Although, it seems that it shouldn't add more html to your output. It is odd that you don't see that output when you run from the command line. Did you create a sample script to test CGI.pm? Have you tried grepping CGI.pm for the 403 status to see if you can find where that extraneous output is coming from? William -- Lead Developer Knowmad Services Inc. || Internet Applications & Database Integration http://www.knowmad.com --------------------------------------------------------------------- Web Archive: http://www.mail-archive.com/[email protected]/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
