Re: [Rabbit-proxy-development] 060404: BUG REPORT - Rabbit pre-3.1 error messages - incorrect handling of user authorisation for SSL connections

[Robert O. <ro...@kh...>]

Matej Mihelic wrote:
> I think the Rabbit performs incorrect handshake over SSL when combined 
> with user authentification.

It seems to work for me. I get:
HTTP_CODE: 301 both if I specify --proxy-user or not.

Note: rabbit does not run any http filters on CONNECT requests (that is 
probably a bug). Rabbit do run the ip filters though.

> I get the following line in access.log:
> 172.16.33.70 - - 04/apr/2006:12:39:11 GMT "CONNECT 
> updates.mozilla.org:443 HTTP/1.0" 200 -

Seems normal. Note that the status code in rabbits access_log is the
status code for rabbit, not the status code from the real server.
Rabbit handled this connection without problems so it is a 200 Ok.
If the resource had a http header with a status of 500, 404, 301 or 200 
does not really matter to rabbit.

> And the following line in the error.log:
> [04/apr/2006:12:44:33 GMT][WARN][Tunnel: failed to handle: 
> java.io.IOException: An existing connection was forcibly closed by the 
> remote host]

Yes the tunnel does not always understand nicely when the connection is 
closed. So sometimes it logs. This is not a problem.

> Without Rabbit3 in between I'll get the following HTTP CODE: 301

/robo