httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From r..@ai.mit.edu (Robert S. Thau)
Subject Re: [hartill@ooo.lanl.gov: Re: custom error responses revistited]
Date Tue, 28 Mar 1995 13:04:55 GMT
   From: rst@ai.mit.edu (Robert S. Thau)
   Date: Tue, 28 Mar 95 12:56:56 EST

   Has anyone tried the NCSA 1.4 custom responses ? I found working
   from apache 0.3 that depending on what type of document you
   rediected to had all kinds of side-effects. Redirecting to a plain
   html doc was okay, redirecting to a cgi-script or to a server-side
   includes doc caused all sorts of problems and fixing one broke it
   somewhere else, and some problems only became evident after a SIGHUP, with
   global variables failing to be initialised for a redirect.

I haven't tried them yet personally.  However, to judge by the
hypernews bboard the NCSA folks are running for beta testers, other
people have and it does seem to basically work.  (The only problem
I've seen noted to date is the obvious one, that relative URLs in the
returned text are interpreted relative to the document that caused the
error, which means that <img href="skull.gif">, with skull.gif in the
same directory as the error script, will not work as intended). 

FWIW, the NCSA code does the redirection to the error document by
making a recursive call to handle_get, as when a script returns a
local URL in 'Location: ', and that mechanism seems to work OK (I've
even written CGI scripts which invoke other CGI scripts indirectly by
this means, and it works).

   I'll try to cleanup the code and upload sometime today, maybe.

   rob

Looking forward to it.

rst


Mime
View raw message