Closed Bug 1053744 Opened 12 years ago Closed 12 years ago

blog.mozilla.com/* are redirected to blog.mozilla.org, resulting in broken feed URLs and content

Categories

(Infrastructure & Operations :: IT-Managed Tools, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: flod, Assigned: jd)

References

Details

(Whiteboard: [kanban:https://kanbanize.com/ctrl_board/4/759] )

According to my feed reader logs it started between 12 AM and 1 PM CET time. All blog.mozilla.com URLs are redirecting to blog.mozilla.org/, resulting in broken feed URLs, and most important in broken posts across websites. Example: l10n blog http://blog.mozilla.com/l10n/ Get redirected to http://blog.mozilla.org/ And posts are missing images. Example https://blog.mozilla.org/l10n/2014/08/05/awesome-l10n-contributor-biraj-karmakar/
Assignee: server-ops → jcrowe
Component: Server Operations → WebOps: IT-Managed Tools
Product: mozilla.org → Infrastructure & Operations
QA Contact: shyam → nmaul
Whiteboard: [kanban:https://kanbanize.com/ctrl_board/4/759]
The redirect issue has been resolved. It was a match issue for the target, it was not including the original request after the /. I will look into the image issue.
Wow, so I finally got this one figured out. It was a bit time consuming because everything was working correctly in the dev environment (which is why we went to prod with yesterdays changes). It turned out that sometime in the distant past someone was testing a caching plugin (in prod) and left an errant .htaccess file lying around (deep in the filesystem). This caused things under two particular upload paths to redirect incorrectly and serve the internal 404 instead of the actual file. I have removed that .htaccess file and removed the test plugin as well. I also spoke with the person and asked them to dev in dev next time, so this issue should not reoccur. Sorry for the inconvenience, and please let me know if you see anything else that is not right. Regards
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.