RE: New Version Notification for draft-nottingham-httpbis-retry-01.txt

Happy to see this updated.

Ironic note:  I currently own two different HTTP stacks with divergent behaviors here.  In the past week, we have received two bug reports about this topic.

  *   One of the stacks doesn't retry failed POST requests; this was reported as a bug, because a failed request should be retried if it didn't reach the server
  *   One of the stacks retries failed POST requests in some circumstances; this was reported as a bug, because the RFC says POSTs shouldn't be retried automatically

From: Mark Nottingham [mailto:mnot@mnot.net]
Sent: Wednesday, February 1, 2017 12:26 AM
To: HTTP Working Group <ietf-http-wg@w3.org>
Subject: Fwd: New Version Notification for draft-nottingham-httpbis-retry-01.txt

FYI; fairly minor update. Would love to hear what people think about the various suggested paths forward.

Cheers,




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/