[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #13788 [Tor Browser]: Meek bridges don't work in TB 4.5alpha1
#13788: Meek bridges don't work in TB 4.5alpha1
-----------------------------+----------------------
Reporter: cypherpunks | Owner: tbb-team
Type: defect | Status: new
Priority: normal | Milestone:
Component: Tor Browser | Version:
Resolution: | Keywords: meek
Actual Points: | Parent ID:
Points: |
-----------------------------+----------------------
Comment (by dcf):
Replying to [comment:4 mcs]:
> Regarding the other problem, looking here:
> http://mxr.mozilla.org/mozilla-
esr31/source/netwerk/protocol/http/HttpBaseChannel.cpp#1232
> it seems like the request did not complete successfully. I am not sure
why that would be the case, but I think the onStopRequest code should
execute a test like this:
> {{{
> if (Components.isSuccessCode(status)) {
> }}}
> before trying to access responseStatus.
We already do the `isSuccessCode(status)` check a couple of lines later,
at [https://gitweb.torproject.org/pluggable-
transports/meek.git/blob/refs/tags/0.11:/firefox/components/main.js#l398
main.js:398]. The error is happening at main.js:396 when trying to index
`context`, not when reading `status`.
There's something internal to Tor Browser that is blocking the request.
It's not just a remote server errorâthose already happen frequently in
normal use and the code handles them. Something (something new in
4.5-alpha-1) is preventing the request from even being sent. We can make
the code handle this case gracefully, but we'll also have to find out what
prevents the requests from being sent in order for the pluggable transport
to work.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/13788#comment:5>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs