[9663] in www-talk@info.cern.ch
Re: CGI & Location
daemon@ATHENA.MIT.EDU (Brandon Long)
Wed Jan 24 12:00:00 1996
To: drtr1@cus.cam.ac.uk (David Robinson)
Date: Wed, 24 Jan 1996 10:56:47 -0600 (CST)
Cc: www-talk@w3.org
In-Reply-To: <m0tf5Xs-000DJLC@ursa.cus.cam.ac.uk> from "David Robinson" at Jan 24, 96 01:47:00 pm
From: Brandon Long <blong@uiuc.edu>
Resent-From: www-talk@w3.org
Last time, David Robinson uttered the following other thing:
>
> What should a server do if a script returns
>
> Location: /an/otherfile
> Myheader: value
>
> should it
> a) ignore the Myheader, and simply act as if /an/otherfile was requested
> b) return /an/otherfile but add the Myheader header?
>
> If b), should the headers added by the script take precedence over headers
> appropriate for the new document?
>
> Apache and NCSA <= 1.3 do (a). I have heard a rumour that NCSA 1.5 does (b).
> I receiveda request from a user who wants Apache to do (b) so that he
> can add netscape 'Window-Target:' headers to the servers respose.
1.5 does (a) as well, at least from my test. Looking at the code,
this should indeed be the case.
> I'd appreciate any input so that I can get a concensus to settle this point
> for the CGI specification.
Would a mechanism to allow the user to specify extra headers for urls
work better? It seems kinda heavyweight to launch a CGI script just to
add a header.
Brandon
--
Brandon Long "I think, therefore, I am confused." -- RAW
HTTPd/SDG/NCSA "Of all the things I've lost, I miss my mind the most."
ECE/UIUC blong@uiuc.edu http://www.uiuc.edu/ph/www/blong
N9WUC Don't worry, these aren't even my views.
