[9404] in www-talk@info.cern.ch
Re: what's a CGI to do?...
daemon@ATHENA.MIT.EDU (Thomas Maslen)
Sun Dec 3 23:03:07 1995
To: dmk@allegra.att.com (Dave Kristol)
Cc: koen@win.tue.nl, www-talk@w3.org
In-Reply-To: Your message of "Thu, 30 Nov 1995 10:31:30 EST."
<9511301532.AA26478@ig2.att.att.com>
Date: Sun, 03 Dec 1995 19:50:48 -0800
From: Thomas Maslen <tmaslen@verity.com>
Resent-From: www-talk@w3.org
[ A tardy reply to a discussion last Thursday about "local" redirects: ]
> Perhaps a server can/should only handle internally GET and HEAD?
I think that's the right choice.
(I'm assuming that "local" redirects are strictly intended to be a performance
optimization, which can be used only when the net effect is the same as that
of a real redirect. Given that, I think that there are just too many hairy
issues surrounding POST, both semantics and implementation issues, for it to
be handled by an internal redirect. Even if the CGI script indicates a local
redirect, I think the HTTP daemon should turn it into a real redirect).
Thomas Maslen
tmaslen@verity.com
