Search the archives!
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Full-disclosure] abnormal behavior Gmail logon
- From: eaton.lists at gmail.com (Brian Eaton)
- Subject: [Full-disclosure] abnormal behavior Gmail logon
- Date: Wed May 31 13:25:31 2006
On 5/31/06, Valdis.Kletnieks@xxxxxx <Valdis.Kletnieks@xxxxxx> wrote: > On Wed, 31 May 2006 09:23:08 BST, Edward Pearson said: > > This isn't abnormal or weird, It happens when your internet connection > > is fairly slow and its because you sometimes receive incomplete headers > > for the page (broken or garbled) > > If you have noisy hardware that's mangling data in transit, the mangling will > *usually* be detected by the checksums on each IP packet. The reason your > connection gets slow is because if a corruption is detected, the packet gets > thrown out, and needs to be retransmitted by the sending system. It is actually possible that the data sent in the HTTP connection is getting mangled even though the TCP checksums are correct. In one mode of operation, HTTP allows a server to indicate when a document is complete simply by closing a TCP connection. If the server gets busy, it might decide your client is just too slow to be worth dealing with and close the connection early. 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. Regards, Brian
- References:
- [Full-disclosure] abnormal behavior Gmail logon
- From: Edward Pearson
- [Full-disclosure] abnormal behavior Gmail logon
- From: Valdis.Kletnieks@xxxxxx
- [Full-disclosure] abnormal behavior Gmail logon
- Prev by Date: [Full-disclosure] GnuPG fun
- Next by Date: [Full-disclosure] SUSE Security Announcement: cron local privilege escalation (SUSE-SA:2006:027)
- Previous by thread: [Full-disclosure] abnormal behavior Gmail logon
- Next by thread: [Full-disclosure] abnormal behavior Gmail logon
- Index(es):