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 2002/08/09 08:20:07 UTC
DO NOT REPLY [Bug 11580] New: -
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
Summary: generate Content-Location headers
Product: Apache httpd-2.0
Version: 2.0.39
Platform: All
OS/Version: All
Status: NEW
Severity: Enhancement
Priority: Other
Component: mod_dir
AssignedTo: bugs@httpd.apache.org
ReportedBy: bugs.apache.org@mnot.net
The Content-Location HTTP header indicates an alternate location for the
entity associated with a message. This much underused facility could be very
useful to agents and automated systems like Google, in order to get a richer
understanding about the relationship between resources.
For example, if mod_dir were to generate a C-L header for requests to "/":
Content-Location: /index.html
and likewise requests for /index.html:
Content-Location: /
Google would know that the representations it stores for each are equivalent,
rather than just assuming so by using a heuristic.
This is a low-cost way to add some intelligence to the Web. Please consider
adding C-L to mod_dir. Thanks!
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org