- From: James M Snell <jasnell@gmail.com>
- Date: Tue, 3 Nov 2015 07:36:40 -0800
- To: "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
Quick non-trolling question: the HTTP/2 RFC currently deals with replay of idempotent requests that likely have not yet been handled but I note that the issue over multiplexing non-safe methods was never addressed. Has a recommended best practice emerged among implementations for ensuring that unsafe requests are not sent or handled out of order? Or is it considered to simply be up to individual implementations to figure out?
Received on Tuesday, 3 November 2015 15:37:31 UTC