- From: Alex Rousskov <rousskov@measurement-factory.com>
- Date: Mon, 6 Feb 2017 14:04:30 -0700
- To: HTTP Working Group <ietf-http-wg@w3.org>
- Cc: Mark Nottingham <mnot@mnot.net>
On 02/01/2017 01:26 AM, Mark Nottingham wrote: > FYI; fairly minor update. Would love to hear what people think about the > various suggested paths forward. FWIW, Squid mind-boggling algorithm for retries is partially summarized at http://wiki.squid-cache.org/SquidFaq/InnerWorkings?highlight=%28reforward%29#When_does_Squid_re-forward_a_client_request.3F Your draft already mentions a single Squid decision point, but the actual logic is a lot more complex than the draft currently implies. Some of that complexity is Squid's fault, as the source code comment you quoted illustrates, but a lot of it is genuine. Recommending a unified (but necessarily parameterized) approach to retries would be useful for future implementors, but I suspect that doing so properly would take too much time while oversimplifying the situation would not help much. Just cataloging various retry factors to consider may be very helpful on its own, even if you then suggest nothing more than "keep these factors in mind when implementing retries". Thank you, Alex. >> Begin forwarded message: >> >> *From: *internet-drafts@ietf.org <mailto:internet-drafts@ietf.org> >> *Subject: **New Version Notification for >> draft-nottingham-httpbis-retry-01.txt* >> *Date: *1 February 2017 at 7:25:43 pm AEDT >> *To: *"Mark Nottingham" <mnot@mnot.net <mailto:mnot@mnot.net>> >> >> >> A new version of I-D, draft-nottingham-httpbis-retry-01.txt >> has been successfully submitted by Mark Nottingham and posted to the >> IETF repository. >> >> Name:draft-nottingham-httpbis-retry >> Revision:01 >> Title:Retrying HTTP Requests >> Document date:2017-02-01 >> Group:Individual Submission >> Pages:18 >> URL: >> https://www.ietf.org/internet-drafts/draft-nottingham-httpbis-retry-01.txt >> Status: >> https://datatracker.ietf.org/doc/draft-nottingham-httpbis-retry/ >> Htmlized: >> https://tools.ietf.org/html/draft-nottingham-httpbis-retry-01 >> Diff: >> https://www.ietf.org/rfcdiff?url2=draft-nottingham-httpbis-retry-01 >> >> Abstract: >> HTTP allows requests to be automatically retried under certain >> circumstances. This draft explores how this is implemented, >> requirements for similar functionality from other parts of the stack, >> and potential future improvements. >> >> >> >> >> Please note that it may take a couple of minutes from the time of >> submission >> until the htmlized version and diff are available at tools.ietf.org >> <http://tools.ietf.org>. >> >> The IETF Secretariat >> > > -- > Mark Nottingham https://www.mnot.net/ >
Received on Monday, 6 February 2017 21:05:00 UTC