You are viewing a plain text version of this content. The canonical link for it is here.
Posted to bugs@httpd.apache.org by bu...@apache.org on 2003/03/04 16:35:47 UTC
DO NOT REPLY [Bug 11580] -
generate Content-Location headers
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11580>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11580
generate Content-Location headers
nd@perlig.de changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |WONTFIX
------- Additional Comments From nd@perlig.de 2003-03-04 15:35 -------
I don't believe, that it's so useful at all. RFC 2616, 14.14 says:
A cache cannot assume that an entity with a Content-Location
different from the URI used to retrieve it can be used to respond to
later requests on that Content-Location URI.
But that is actually, what you want. Further it's probably not desired to send
something like
Content-Location: /cgi-bin/generate-index.cgi
If the resource (say, index.html) is content-negotiated, the Content-Location
will be set anyway (by mod_negotiation, of course).
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org