Bug 45257

Summary: add (en)force option for UseCanonicalName
Product: Apache httpd-2 Reporter: Matus "fantomas" Uhlar <uhlar>
Component: CoreAssignee: Apache HTTPD Bugs Mailing List <bugs>
Status: REOPENED ---    
Severity: enhancement Keywords: MassUpdate
Priority: P2    
Version: 2.4-HEAD   
Target Milestone: ---   
Hardware: All   
OS: All   

Description Matus "fantomas" Uhlar 2008-06-23 06:07:56 UTC
Please add option "force" or "enforce" to UseCanonicalName directive, which whould redirect the client to the same relative URL with canonical name of server, if name other thhan ServerName (usually ServerAlias) was specified.
It can be done now only by defining 2 virtual hosts, which is not as easy for many virtualhosts.
Comment 1 William A. Rowe Jr. 2018-11-07 21:08:11 UTC
Please help us to refine our list of open and current defects; this is a mass update of old and inactive Bugzilla reports which reflect user error, already resolved defects, and still-existing defects in httpd.

As repeatedly announced, the Apache HTTP Server Project has discontinued all development and patch review of the 2.2.x series of releases. The final release 2.2.34 was published in July 2017, and no further evaluation of bug reports or security risks will be considered or published for 2.2.x releases. All reports older than 2.4.x have been updated to status RESOLVED/LATER; no further action is expected unless the report still applies to a current version of httpd.

If your report represented a question or confusion about how to use an httpd feature, an unexpected server behavior, problems building or installing httpd, or working with an external component (a third party module, browser etc.) we ask you to start by bringing your question to the User Support and Discussion mailing list, see [https://httpd.apache.org/lists.html#http-users] for details. Include a link to this Bugzilla report for completeness with your question.

If your report was clearly a defect in httpd or a feature request, we ask that you retest using a modern httpd release (2.4.33 or later) released in the past year. If it can be reproduced, please reopen this bug and change the Version field above to the httpd version you have reconfirmed with.

Your help in identifying defects or enhancements still applicable to the current httpd server software release is greatly appreciated.
Comment 2 Matus "fantomas" Uhlar 2018-11-08 08:12:39 UTC
The option is still not available, I'm reopening this