On 3/11/07, Henrik Nordstrom <[EMAIL PROTECTED]> wrote:
sön 2007-03-11 klockan 16:38 +0800 skrev Adrian Chadd:
> If someone would like a fun weekend project - write something to sniff
> out these broken connections and insert temporary ip routes for it.
Another idea would be a test tool to see why a site is broken..
Known issues:
- ECN
- Window Scaling
- Forgetting Vary
- Mixing up ETag (same ETag on multiple incompatible entities)
- Various malformed responses
* Double content length
* Malformed headers
* Repeated single-value headers
If I knew more about the structure of these items I'd give it a whirl.
As it is, I just have come up to the bottom level of understanding tcp
window scaling.
FWIW, I complained to the ncsecu and got a call from their IT dept
today. It seems that using the words "firewall," "bank," and "broken"
in the same sentence caused a stir. Apparently they did an OS upgrade
on their Symantec (?) firewall recently. I'm not the only one
complaining. We'll see if Symantec fixes it.
Thanks for the help again, Henrik. I would have been lost on this one
without it.
Chris
