- From: Nicolas Mailhot <nicolas.mailhot@laposte.net>
- Date: Mon, 3 Mar 2014 12:31:18 +0100
- To: "Rob Trace" <Rob.Trace@microsoft.com>
- Cc: "Patrick McManus" <pmcmanus@mozilla.com>, "William Chan (陈智昌)" <willchan@chromium.org>, "Josh Goodall" <joshua.goodall@gmail.com>, "IETF HTTP WG" <ietf-http-wg@w3.org>
Le Lun 3 mars 2014 11:13, Rob Trace a écrit : > +1. In addition, there is a bad case here where adding a new level of DNS > query is subject to packet loss 1% of the time which can incur a long > timeout. Actually, since there is no "DNS error" code in http1 proxy communication, if proxy operators do not want to be buried under user complains each time a popular site has dns problems, they have to force dns resolution in the browser before relaying any request to the proxy (which will then perform a second resolution) That's the only way to get browsers display a dns error page and not a evil proxy error page when dns is down So complaining of srv now, but ignoring proxy connexion error handling, is kind of sad. Regards, -- Nicolas Mailhot
Received on Monday, 3 March 2014 11:32:09 UTC