Closed Bug 855907 Opened 11 years ago Closed 11 years ago

input.mozilla.com should forward to input.mozilla.org

Categories

(Input :: General, defect)

x86_64
Windows 7
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: kbrosnan, Assigned: cturra)

Details

(Whiteboard: [triaged 20130329])

input.mozilla.com should forward to input.mozilla.org

I get a forbidden error using my input.mozilla.com bookmark.
I'm puzzled. If I go to input.mozilla.com it redirects me to https://input.mozilla.org/en-US/ . Seems to be working fine.

What's the exact url for your bookmark?
I am using Firefox for Android. https://input.mozilla.com I get a 403 forbidden error.
Chris: Seems http://input.mozilla.com/ redirects correctly to the right input.mozilla.org place, but https://input.mozilla.com/ doesn't redirect at all.

Can we get https://input.mozilla.com/ to redirect to https://input.mozilla.org/ ?
during our deployment, we spoke about now supporting this. the main reason is because we do ssl termination on the load balancer and currently only have a signed certificate for input.mozilla.org. at that time we made the call we would *not* add support a redirect for https://input.mozilla.com.
i went ahead and added the redirect. hopefully browsers do not complain about the certificate mismatch (the certificate common name is for input.mozilla.org and the request uri is input.mozilla.com). my initial testing with firefox nightly seems good and `curl` is happy too ;)

 $ curl -I https://input.mozilla.com
 HTTP/1.1 301 Moved Permanently
 Server: Apache
 X-Backend-Server: input1.webapp.phx1.mozilla.com
 Vary: Accept-Encoding
 Content-Type: text/html; charset=iso-8859-1
 Date: Sat, 30 Mar 2013 01:17:34 GMT
 Location: https://input.mozilla.org/
 Transfer-Encoding: chunked
 Connection: Keep-Alive
 X-Cache-Info: caching
Assignee: nobody → cturra
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Whiteboard: [triaged 20130329]
Thanks Chris!

Kevin: Does your bookmark work now?
You need to log in before you can comment on or make changes to this bug.