Closed grahamperrin closed 4 years ago
Well, I'm leaving this open for a while to see if we can at least manage to reproduce it.
… I can not get this …
Well d'uh, Graham, you'll not get the interception page if your first step is to disable interception. Opening post corrected!
Here, although I imagine that it will be difficult to reproduce:
The screen recording from which those frames are taken:
2019-12-05 13:55.mp4
https://put.re/player/Kjx8fXLf.mp4Watch from 08:23 on the timeline for alternative (more exotic) steps to production of the issue – setting an inappropriate URL as the home page – although again, I doubt that it will be consistently reproducible in this way.
HTH.
It's a curiosity, doesn't smell like something that might be encountered through normal usage. Could be me thrashing things again; at one point during the recording I did pause for a minute or so (I didn't bother to pause at other times).
I accidentally closed this, but version 0.11.1
might have fixed it.
Finally got around to testing this, and I also noticed other minor issues in the process.
I fixed them all in 0.11.3
. Thank you for reporting :+1: You deserve a cookie 🍪
DisableEnable interception of server-initiated redirections to httpmaybe also disableenable handling of non-standard redirections to http… at least twice I found version 0.11.0b7 not proceeding – IIRC just a blank white extensions page – but (sorry) I didn't take a screenshot
and now I can't reproduce the behaviour.More specifically, I can not get this after step (3):