The websites opens a new window if it is called by an https request which isn't "Native". So we get in kind of an odd loop I guess. Because the website supports https but tries to downgrade us. We receive responses to our https requests, so we won't downgrade.
Bug 1715253 Comment 2 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
The websites tries to redirect to its http site if it is called by an https request which isn't "Native". So we get in kind of an odd loop I guess. Because the website supports https but tries to downgrade us. We receive responses to our https requests, so we won't downgrade.
The websites tries to redirect to its http site if it is called by an https request which isn't "Native". So we get in kind of an odd loop I guess. Because the website supports https but tries to downgrade us. We receive responses to our https requests, so we won't downgrade. Summarized: 1. We request `https://radio.garden/visit/berlin/6lcXHtKK` 2. `https://radio.garden/visit/berlin/6lcXHtKK` checks from which place we are calling it 3. Page wants to downgrade us by redirecting us to `http://radio.garden/visit/berlin/6lcXHtKK` 4. We upgrade the redirection and start to again at stage (1)
The websites tries to redirect to its http site if it is called by an https request which isn't "Native". So we get in kind of an odd loop I guess. Because the website supports https but tries to downgrade us. We receive responses to our https requests, so we won't downgrade. Summarized: 1. We request `https://radio.garden/visit/berlin/6lcXHtKK` 2. `https://radio.garden/visit/berlin/6lcXHtKK` checks from which place we are calling it 3. Page wants to downgrade us by redirecting us to `http://radio.garden/visit/berlin/6lcXHtKK` 4. We upgrade the redirection and start again from stage (1)