Closed Bug 532199 Opened 15 years ago Closed 15 years ago

HTTP and HTTPS for abuchanan-sfx.khan.m.o and spreadfirefox.authstage

Categories

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

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: abuchanan, Assigned: oremj)

Details

Hey, I'm looking to work on bug 412354, and I need help setting up apache to support both HTTP and HTTPS on khan and spreadfirefox.stage On khan... My dev site, http://abuchanan-sfx.khan.mozilla.org/ for reference, my config is here, /etc/httpd/conf/domains/abuchanan.k.m.o.conf oremj mentioned I need an ip-based vhost, instead of my usual name-based, and I'm not sure how to set that part up. The end goal is being able to visit abuchanan-sfx.khan.mozilla.org and spreadfirefox.stage.mozilla.com from both HTTP and HTTPS. Please. Thanks. Let me know if I can help.
Using a name-based host is fine, as long as its the only domain that needs SSL on the box (or there's a wildcard cert on the box, which is probably the easiest thing to do if that's nor already the case.).
Assignee: server-ops → mrz
Guys: Can we pick this back up?
Assignee: mrz → jeremy.orem+bugs
Yo IT: Can we get this going? Pretty please :)
Alex, I've put zlb-stage in front of khan, so you can put vhosts behind it. Ex: http://oremj.zeus.khan.mozilla.org/test.php -> zlb-stage01:80 -> khan:80 https://oremj.zeus.khan.mozilla.org/test.php -> zlb-stage01:443 -> khan:81 See the oremj.zeus.khan.mozilla.org VirtualHost @ khan:/etc/httpd/conf/domains/oremj.khan.mozilla.org.conf for an example. Any more information needed?
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
I think I can set up what I need on khan with your example. Reopening because we need to figure out how to make SFx stage work the same way, accessible from both HTTP and HTTPS Thanks
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
All set.
Status: REOPENED → RESOLVED
Closed: 15 years ago15 years ago
Resolution: --- → FIXED
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.