Re: [PATCH] http-backend: allow empty CONTENT_LENGTH

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: [PATCH] http-backend: allow empty CONTENT_LENGTH
From: Max Kirillov <max@xxxxxxxxxx>
Date: Fri, 7 Sep 2018 07:59:26 +0300
Cc: Junio C Hamano <gitster@xxxxxxxxx>, Jonathan Nieder <jrnieder@xxxxxxxxx>, Jelmer Vernooĳ <jelmer@xxxxxxxxx>, git@xxxxxxxxxxxxxxx
In-reply-to: <20180907033831.GB1383@sigill.intra.peff.net>
References: <20180906193516.28909-1-max@max630.net> <xmqq1sa6z3zp.fsf@gitster-ct.c.googlers.com> <20180907032740.GA20545@jessie.local> <20180907033831.GB1383@sigill.intra.peff.net>

Actually, another reason for the latest issue was that CONTENT_LENGTH
is parsed for GET requests at all. It should be parsed only for POST
requests, or, rather, only for upoad-pack and receive-pack requests.

Follow-Ups:
- Re: [PATCH] http-backend: allow empty CONTENT_LENGTH
  - From: Junio C Hamano

References:
- [PATCH] http-backend: allow empty CONTENT_LENGTH
  - From: Max Kirillov
- Re: [PATCH] http-backend: allow empty CONTENT_LENGTH
  - From: Junio C Hamano
- Re: [PATCH] http-backend: allow empty CONTENT_LENGTH
  - From: Max Kirillov
- Re: [PATCH] http-backend: allow empty CONTENT_LENGTH
  - From: Jeff King

Prev by Date: Re: [PATCH] http-backend: allow empty CONTENT_LENGTH
Next by Date: Temporary git files for the gitdir created on a separate drive in workdir
Previous by thread: Re: [PATCH] http-backend: allow empty CONTENT_LENGTH
Next by thread: Re: [PATCH] http-backend: allow empty CONTENT_LENGTH
Index(es):
- Date
- Thread

[Index of Archives] [Linux Kernel Development] [Gcc Help] [IETF Annouce] [DCCP] [Netdev] [Networking] [Security] [V4L] [Bugtraq] [Yosemite] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Linux SCSI] [Fedora Users]

Powered by Linux