Closed
Bug 1281567
Opened 8 years ago
Closed 7 years ago
Make hardhat redirects nicer
Categories
(Infrastructure & Operations Graveyard :: WebOps: Other, task)
Infrastructure & Operations Graveyard
WebOps: Other
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: fubar, Unassigned)
References
Details
(Whiteboard: [kanban:https://webops.kanbanize.com/ctrl_board/2/3144])
Moving over from bug 1279952#c24 (In reply to Matthew N. [:MattN] (behind on reviews) from comment #24) > Please can we avoid doing redirects to https://hardhat.cdn.mozilla.net/ when > there are issues on any site so that session history isn't lost for any tabs > which were pointing to the site. A rewrite/proxy rule can preserve the URL > in the address bar while still showing the hardhat site. Having the URLs > return a iframe pointing to https://hardhat.cdn.mozilla.net/… would also > work. Doing what I suggest would also mean we would be returning a more > appropriate HTTP error code (e.g. 503) instead of 302.
We very rarely use Hardhat redirects on the WebOps side, and while I agree in theory with the request, in practice we should not change this behavior. I assume that whoever is using Hardhat redirects is trying to get user traffic *away* from the site and *to* the Hardhat CDN. Whether or not that's a *good* idea is up for debate. :fubar, I'm temporarily closing this since there's no opportunity on our side to help you with it right now. If you need something urgently, reach out to me and we'll discuss further. There may be an easy fix that meets any needs here.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INCOMPLETE
Updated•5 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•