httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Paul Richards <p.richa...@elsevier.co.uk>
Subject Apache problem (fwd)
Date Tue, 14 May 1996 14:52:43 GMT
Any comments? 

> The action taken when an error occurs is influenced by the line in srm.conf
> which reads:
> 	ErrorDocument 403 /cgi-bin/errors/403.pl
> The NCSA daemon would catch the error, get the handler document (i.e., start
> the CGI script), and send that document as if it were a new document. This
> includes the generation of header lines, most importantly the statusline,
> which would be
> 	HTTP/1.0 200 Document follows
> The Apache server also gets the handler document, but it retains the
> original status line, which is
> 	HTTP/1.0 403 Forbidden
> indicating that the client does not have access to the requested document.
> 
> Netscape totally ignores the status line, and happily displays the document.
> However, some older versions of Mosaic see that an error occurs, and decide
> that it's better to display everything that follows. This includes header
> information, so Mosaic users of the electronic journals get the header
> information on their screen when they try to enter an access protected area.
> Microsoft Internet Explorer sees the error status line, and generates an
> alerting pop-up window, telling that you do not have access, without
> displaying the document.


-- 
  Paul Richards. Originative Solutions Ltd.  (Netcraft Ltd. contractor)
  Elsevier Science TIS online journal project.
  Email: p.richards@elsevier.co.uk
  Phone: 0370 462071 (Mobile), +44 (0)1865 843155

Mime
View raw message