Closed Bug 528269 Opened 15 years ago Closed 15 years ago

SSL on outgoing.m.o goes to devmo

Categories

(Infrastructure & Operations Graveyard :: WebOps: Other, task)

All
Other
task
Not set
trivial

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: clouserw, Assigned: fox2mike)

Details

https://outgoing.mozilla.org/v1/ redirects to https://developer.mozilla.org/En

We don't need SSL, but it's weird it redirects to devmo.
If you don't need SSL, nothing to see here :)

outgoing is not configured for SSL. So the default fall back is devmo on the generic cluster.
Assignee: server-ops → shyam
URL: I
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → INVALID
We should probably replace port 81 default vserver on the generic cluster.
(In reply to comment #1)
> If you don't need SSL, nothing to see here :)
> 
> outgoing is not configured for SSL. So the default fall back is devmo on the
> generic cluster.

Does that mean this is happening for other sites too?  If https doesn't redirect to http it should just not respond
Status: RESOLVED → REOPENED
Resolution: INVALID → ---
https on non https sites now defaults to mozilla.com over http. If that didn't make much sense, I blame jetlag :D
URL: I
Status: REOPENED → RESOLVED
Closed: 15 years ago15 years ago
Resolution: --- → FIXED
Why are you redirecting to moz.com?  Seems like the proper thing to do would be to redirect to http or not respond on :443.
(In reply to comment #5)
> Why are you redirecting to moz.com?  Seems like the proper thing to do would be
> to redirect to http or not respond on :443.

This was more about changing the default https (port 81) vhost in Apache to something other than devmo.  

Otherwise we'll need to burn an IP per site.
Component: Server Operations: Web Operations → WebOps: Other
Product: mozilla.org → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.