#5477: Surprising DOM origins before HTTPS-E/NoScript redirects have completed
-------------------------------------+--------------------------------------
Reporter: Drugoy | Owner: ma1
Type: defect | Status: reopened
Priority: blocker | Milestone:
Component: EFF-HTTPS Everywhere | Version:
Resolution: | Keywords:
Parent: | Points:
Actualpoints: |
-------------------------------------+--------------------------------------
Comment(by pde):
I performed the experiment that mikeperry suggested, testing each of our
rewriting paths separately.
Disabling the shouldLoad / forceURI path did not stop the bug.
Disabling the http-on-modify-request / replaceChannel path ''did'' stop
the bug. So unsuprisingly, we're looking at a bug in replaceChannel.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/5477#comment:38>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
[email protected]
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
