Closed Bug 1113702 Opened 10 years ago Closed 9 years ago

Non-SSL blog.mozilla.org URL is not redirected to https

Categories

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

Product:
Infrastructure & Operations Graveyard
Component:
WebOps: Other
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: kohei, Assigned: nmaul)

Details

(Whiteboard: [kanban:https://webops.kanbanize.com/ctrl_board/2/187] ) 

I just noticed this when I checked the Add-ons Blog. I thought it was redirected before.

http://blog.mozilla.org/ -> https://blog.mozilla.org/
Assignee: nobody → server-ops
Component: blog.mozilla.org → Server Operations
Product: Websites → mozilla.org
QA Contact: shyam
Version: unspecified → other
Summary: Non-SSL URL is not redirected to https → Non-SSL blog.mozilla.org URL is not redirected to https
Assignee: server-ops → server-ops-webops
Component: Server Operations → WebOps: Other
Product: mozilla.org → Infrastructure & Operations
QA Contact: shyam → nmaul
Whiteboard: [kanban:https://webops.kanbanize.com/ctrl_board/2/187]
Assignee: server-ops-webops → nmaul
This is resolved now. Thanks for noticing and opening a bug about it! It definitely used to be redirected, but that fell off during an infrastructure redesign some time ago. :)
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
The blog home page LGTM, but other pages are also redirected to the home page, like this:

http://blog.mozilla.org/blog/2015/02/11/a-watershed-moment-to-protect-the-free-and-open-web/
-> https://blog.mozilla.org/

http://blog.mozilla.org/addons/
-> https://blog.mozilla.org/

Can you check the config again?
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Great catch! I've changed it to preserve the path as well now. Thank you again!
Status: REOPENED → RESOLVED
Closed: 9 years ago → 9 years ago
Resolution: --- → FIXED
Yay!
Status: RESOLVED → VERIFIED
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.