[tor-bugs] #6486 [EFF-HTTPS Everywhere]: Need non-fallback to http option
Tor Bug Tracker & Wiki
blackhole at torproject.org
Fri Dec 21 07:24:15 UTC 2012
#6486: Need non-fallback to http option
-------------------------------------+--------------------------------------
Reporter: grarpamp | Owner: pde
Type: defect | Status: reopened
Priority: normal | Milestone:
Component: EFF-HTTPS Everywhere | Version:
Resolution: | Keywords:
Parent: | Points:
Actualpoints: |
-------------------------------------+--------------------------------------
Changes (by grarpamp):
* status: closed => reopened
* resolution: invalid =>
Comment:
This ticket does not concern javascript content loops, it concerns
protocol loops.
> Unless...
Yes, thought this was answered on 2012-09-15.
Again, if browser is fed an http uri, https-e remaps it to https and sends
it to server, and then if the https server returns protocol error, or
plain doesn't respond, I don't want https-e hiding that server message or
browser timeout from me (and possibly also falling back).
And if the server protocol 302's it back to http, I don't want https-e
taking that 302 to http directive, remapping it again to https, sending it
again, looping around with that for a while till finally giving up and
using the server's 302 to http, and staying http thereafter.
So an option to disable the fallback after loop detected, aka: don't use
http ever.
And an option to just quit that uri on error or timeout, aka: show me.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/6486#comment:4>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
More information about the tor-bugs
mailing list