683177 - Response "200 - Tunnel established" instead of "200 - OK"

Status: RESOLVED INCOMPLETE

(Core :: Networking: HTTP, defect)

Description

[Jonah]

Attachment: Request and response data for XMLHttpRequest using Firefox and Safari both used once with and once without Tor.

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_6_8) AppleWebKit/534.50 (KHTML, like Gecko) Version/5.1 Safari/534.50

Steps to reproduce:

Using https://www.pidder.com/ with Firefox (confirmed with versions 4 through 6) over the Tor network (both current and previous Vidalia bundle, current is 0.2.2.32, proxy was the bundled polipo with default configuration). 

Editing or creating a card segment in pidder triggers an XMLHttpRequest that does not reach the server (see attachment).


Actual results:

The response status was "200 - Tunnel established" when inspected in Firebug. The request never reached our server, and consequently the response was empty.


Expected results:

The response status should be "200 - OK" and the request should make it through to the server as it does when using e.g. Firefox without Tor or Safari both with and without Tor (see attachment).

We addressed this problem with the Tor mailing list as well, but since the behavior only seems to occur with Firefox and not with e.g. webkit browsers nor with opera, it might very well be Firefox specific.

Comment 1

[Jo Hermans]

Isn't it the server that generates the message ? I don't know why it reacts differently on a Firefox message than a Safari message.

Besides ... the text is not important in the response, it can be whatever it likes. It's the response-code (200) that is important.

Comment 2

[Boris Zbarsky [:bzbarsky]]

A pcap of the actual traffic in Firefox when using Tor would be useful here.

Comment 3

[Jonah]

(In reply to Jo Hermans from comment #1)
> Isn't it the server that generates the message ? I don't know why it reacts
> differently on a Firefox message than a Safari message.
> 
> Besides ... the text is not important in the response, it can be whatever it
> likes. It's the response-code (200) that is important.

It is definitely not *our* server generating that message. We can verify in our log files that the request never reaches our server.

Comment 4

[Jonah]

Attachment: tcpdump for request that does *not* reach destination server

Comment 5

[Jonah]

Attachment: tcpdump for request that does reach destination server

Comment 6

[Jonah]

Attachment: Tor log for request that does *not* reach destination server

Comment 7

[Jonah]

Attachment: Tor log for request that does reach destination server

Comment 8

[Jonah]

(In reply to Boris Zbarsky (:bz) from comment #2)
> A pcap of the actual traffic in Firefox when using Tor would be useful here.

I have attached tcpdumps and tor log files, respectively, both for requests that do and do not reach the server.

Comment 9

[Boris Zbarsky [:bzbarsky]]

Jonah, thanks.  Any idea which server could be generating that response?  Gecko is certainly not producing HTTP responses.  Perhaps something inside the Tor network?

Patrick, could you take a look at this please?

Comment 10

[Jonah]

(In reply to Boris Zbarsky (:bz) from comment #9)
> Any idea which server could be generating that response? 

My guess is that this response is generated by the polipo proxy. I haven't managed yet to make it write any meaningful logs though.

Comment 11

[Patrick McManus [:mcmanus]]

I'm going to mark this incomplete based on its age and the fact that the caps are text and not .pcap formatted captures.. the text isn't really helpful to me. If the problem persists, please reopen with new data. its not actionable as is. thanks!

Comment 12

[timeless]

https://github.com/jech/polipo/blob/master/tunnel.c