Bug 51718 - Feature Request: Add shorthand to redirect any ServerAlias to the according ServerName
Summary: Feature Request: Add shorthand to redirect any ServerAlias to the according S...
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: mod_alias (show other bugs)
Version: 2.3.12-beta
Hardware: All All
: P2 enhancement (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
Keywords: MassUpdate
Depends on:
Reported: 2011-08-24 20:40 UTC by apafiler
Modified: 2018-11-07 21:09 UTC (History)
0 users


Note You need to log in before you can comment on or make changes to this bug.
Description apafiler 2011-08-24 20:40:30 UTC
I've found this interesting question over at Serverfault.com: http://serverfault.com/questions/301544/how-can-i-redirect-any-serveralias-to-the-respective-servername

The basic idea is to have a shorthand which implies that any ServerAlias should be redirected to the ServerName which is set for the current VirtualHost.

As it's a very common requirement (also due to the current SEO demand) to at least redirect (to) the www-prefixed URL this might be widely used.

As the poster points out this would reduce the risk of configuration errors - by making the config more DRY.
Comment 1 apafiler 2011-11-27 08:29:10 UTC
Maybe mod_macro is a good way to cope with the problem outlined here.
Comment 2 Christophe JAILLET 2013-06-01 08:53:57 UTC
mod_macro will be part of 2.4.5
Comment 3 William A. Rowe Jr. 2018-11-07 21:09:12 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.