git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: bug in HTTP protocol spec

From
Jonathan Nieder <jrnieder@gmail.com>
Date
Feb 22, 2018, 05:37 UTC
Message-ID
<20180222053722.GB133592@aiede.svl.corp.google.com>
In-Reply-To
<89E9DF80-F811-4F7A-AA35-0F52F1180BAF@gmail.com>

(+cc: bmwill@, who is working on protocol v2) Hi,

Dorian Taylor wrote:
> On Feb 21, 2018, at 2:15 PM, Jeff King <peff@peff.net> wrote:
>> Thanks, I agree the document is buggy. Do you want to submit a patch?
>
> Will this do?
Thanks for writing it.

Do you mind if we forge your sign-off? (See Documentation/SubmittingPatches item '(5) Certify your work' for details about what this means.)

> Note I am not sure what the story is behind that `version 1`
> element, whether it's supposed to go before or after the null packet
> or if there should be another null packet or what. Perhaps somebody
> more fluent with the smart protocol can advise.
I believe the 'version 1' goes after the flush-packet.

Thanks, Jonathan

Previous: Dorian TaylorNext: Dorian Taylor
Message 4 of 13 in “bug in HTTP protocol spec”
  1. Dorian TaylorFeb 21, 2018
  2. Jeff KingFeb 21, 2018
  3. Dorian TaylorFeb 21, 2018
  4. Jonathan NiederFeb 22, 2018
  5. Dorian TaylorFeb 22, 2018
  6. Jeff KingFeb 22, 2018
  7. Dorian TaylorFeb 22, 2018
  8. Junio C HamanoFeb 22, 2018
  9. Dorian TaylorFeb 22, 2018
  10. smart-http: document flush after "# service" lineJeff King, Mar 3, 2018
  11. Eric SunshineMar 3, 2018
  12. Jeff KingMar 3, 2018
  13. Brandon WilliamsFeb 22, 2018

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.