httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 44602] New: Options for modfying Content-Location ( relative OR absolute URI)
Date Thu, 13 Mar 2008 22:13:10 GMT
https://issues.apache.org/bugzilla/show_bug.cgi?id=44602

           Summary: Options for modfying Content-Location (relative OR
                    absolute URI)
           Product: Apache httpd-2
           Version: 2.2.4
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: enhancement
          Priority: P4
         Component: mod_negotiation
        AssignedTo: bugs@httpd.apache.org
        ReportedBy: aleksandersen+issues.apache.org@runbox.com


mod_negotiate sets an Content-Location header that cannot be modified. This is
reasoned because it is “protocol critical”.

I would still like to be able to choose whether to include a relative URI or an
absolute URI that is sent from the header.

I fully understand that the server thinks it knows best. But as the protocol
supports both ways and it really would not make anything break by having the
option of including the absolute URI … Well, I do not see the reason not to
let users have that option.

The scenario for including an absolute URI being that I would like a way to
inform users and search engines of the absolute/preferred URI for a resource.
Say I have two domain names—or just a www. and a www.-less version of one
domain—the idea being that I would prefer having users and indexes include
the absolutely preferred URI with the www. prefix or from the most preferred
domain name. Instead of pushing the users/spiders trough a painful 301
redirect, I think it would be a much better practise to simply include an
absolute URI to the resource instead. If a user accesses the resource from the
preferred host, then serving the relative URI seams to be the best option.

  SetEnvIfNoCase Host "^!www.preferred.com$"
header/content-location=absolute-uri

In today’s releases I cannot even unset and manually set the Content-Location
header when it is genereated by mod_negotiation. (Or maybe it is mod_dir that
makes the header. I am not absolutely sure.)

NOTE! I do not know whether this should be filled for the mod_headers component
in stead. Someone who knows are encouraged to modify the bug if it is better
suited there.


-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org


Mime
View raw message