Closed Bug 445615 Opened 17 years ago Closed 17 years ago

Create alias to nl colo's version of mozilla.com

Categories

(mozilla.org Graveyard :: Server Operations, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: samuel.sidler+old, Assigned: oremj)

References

()

Details

When we do releases, nl always lags behind. If Tomcat isn't around to tell us, we might never know if nl never updates without manually setting it up on our machines. Please create a www-nl alias for us to go to and check mozilla.com when on the VPN.
If I add a server alias will the php code automatically redirect to www.mozilla.com?
(In reply to comment #1) > If I add a server alias will the php code automatically redirect to > www.mozilla.com? > It'll redirect to whatever is in the config. so, yeah.
Assignee: server-ops → oremj
Going to WONTFIX this bug. One option for getting this fixed would be to file a bug against mozilla.com to support multiple domain names.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → WONTFIX
(In reply to comment #3) > Going to WONTFIX this bug. One option for getting this fixed would be to file > a bug against mozilla.com to support multiple domain names. > Can you expand on what you mean by this? mozilla.com assumes it's on whatever domain you set in the config file...what would you change?
Maybe we could add an array of domains? We are trying to make an instance of mozilla.com respond on multiple domain names. For example: * We set up a vhost www-nl.mozilla.com, so we can test if nl has been updated, is working correctly, etc. * If we go to www-nl.mozilla.com it will just redirect to www.mozilla.com which will fetch the users local IP, in my case the MPT IP. The other option is just changing /etc/hosts, but that is a bit of a pain for QA or anyone who is monitoring a release or mozilla.com push.
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.