Re: [squid-users] Squid+IWSS HTTPS header problem.

--- Chris Robertson <crobertson@gci.net> escribió:

> Juan Pablo Calomino wrote:
> > I'm seeing something strange.
> >
> > I tail -f access.log|boston, and then i open a
> browser
> > and enter "https://www.bankboston.com.ar", I hit
> > enter, and nothing happens in the tail.
> >
> > Only when I click the "Stop" button, I see:
> > 1169582605.993 8860 xx.xx.xx.xx TCP_MISS/000 95
> > CONNECT www.bankboston.com.ar:443 -
> > FIRST_UP_PARENT/127.0.0.1 -
> >
> > Why can this be?
> >
> > Thanks,
> > Juan Pablo.
> >
> >
> >
>
> Browsers tunnel HTTPS requests via the CONNECT
> method. A tunnel is
> opened at the beginning of the request and closed it
> at the end.
> Requests are not logged until completion (you'd see
> the same thing, with
> a big download over HTTP). The 000 result code
> means the request was
> canceled before any reply was seen.
>
> Chris
>

Thanks Chris,

Now, through Webmin, I've configured an ACL in Squid
so "Safe_ports" fetch directly, because IWSS cannot
scan it.
Anyway, this is what i get when I try to go to
https://www.bankboston.com.ar, and wait...

1169587631.483 440022 10.1.48.24 TCP_MISS/200 39
CONNECT www.bankboston.com.ar:443 -
DIRECT/32.104.16.39 -

I see packets going out, but they never come back.
I also have other proxies and they work ok, so it
shouldn't be a FW problem.

Maybe Websense is doing something wrong, but they
don't say anything.

Regards,
Juan Pablo.

        
                
__________________________________________________
Preguntá. Respondé. Descubrí.
Todo lo que querías saber, y lo que ni imaginabas,
está en Yahoo! Respuestas (Beta).
¡Probalo ya!
http://www.yahoo.com.ar/respuestas
Received on Tue Jan 23 2007 - 14:48:38 MST