> for that matter) and have noticed a *ton* of errors like the
> huge stack trace below regarding broken pipes.
I agree with Stacy Young's thought - it's probably generated when the
browser stops receiving the response, for whatever reason. I've seen similar
"closed pipe" errors on Windows servers. Have you looked at your web server
logs to see if you can find any correlation?
Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
phone: 202-797-5496
fax: 202-797-5444
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
