- From: Nicolas Mailhot <nicolas.mailhot@laposte.net>
- Date: Tue, 17 Jul 2012 21:30:40 +0200
- To: "Julian Reschke" <julian.reschke@gmx.de>
- Cc: "HTTP Working Group" <ietf-http-wg@w3.org>
Le Mar 17 juillet 2012 21:23, Nicolas Mailhot a écrit : > > Le Mar 17 juillet 2012 21:03, Julian Reschke a écrit : >> Could you elaborate? What kind of misbehavior are you referring to? > > Typical misbehaviour is inability to cope with intermediary-inserted > redirect and error codes, and retrying in a loop (because the developer > could not bother to write error handling code, considers that all errors > on the Internet are transient, so with enough retrying he will get > whatever he expected to get at first) > > Then you get the web clients that try to interpret error pages as if they > were whatever they expected to get at first, with sometimes weird results. > > Then you get the 'pump as much as you can' web client that will starve > everything else. (lastly in a corporate environment systems are locked down, apps are supposed to only come in versions the heldesk know to deal with, which has not stopped ISVs from multiplying the web updaters that run sneakily in the background and try to pump new buggy updates no one requested. When we find the user agent of such a beast it ends in the blacklist directly – much less trouble than trying to follow which update web site they use this week) -- Nicolas Mailhot
Received on Tuesday, 17 July 2012 19:31:19 UTC