lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Date: Wed May 31 18:43:12 2006
From: ajaypal at bbsbec.org (Ajay Pal Singh Atwal)
Subject: abnormal behavior Gmail logon

Should'nt the behaviour of a proxy in case of both RST and FIN should be same, i.e always a FIN. As proxy should close the connection **properly** even in case of a failure on the other side.

Sincerely

Ajay Pal Singh Atwal


----- David Farinic <davidfa@....com> wrote:
> >Servers are supposed to send RST packets when they do that, but not
> all
> >servers do it, and not all clients recognize those RST packets as
> >indicating that the document they just downloaded is incomplete
> 
> Most of the clients do recognize and most web servers do correctly
> apply
> use of RST and FIN for TCP/IP HTTP connection ending.
> 
> Problem is that some (most?)Proxy servers (nontransparent and
> probably
> also transparent)  DO NOT. 
> 
> I tested 4 different proxy servers if they pass RST to client's
> browser
> when original web server sent RST. All sent FIN instead of RST :(. (I
> Did this test as I found other web apps. problems resulting from this
> proxy behavior)
> 
> If anybody knows proxy which behaves 'correctly,' pls let me know.
> 
>  
> Regards David Farinic 
> 

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ