summaryrefslogtreecommitdiff
path: root/t/t5562-http-backend-content-length.sh
diff options
context:
space:
mode:
authorMax Kirillov <max@max630.net>2018-09-07 03:36:07 (GMT)
committerJunio C Hamano <gitster@pobox.com>2018-09-07 19:35:51 (GMT)
commit574c513e8dda5598e9e08e8ca2a048bf120a5709 (patch)
treea2088dcfd3318c89bfda556e45c8347b31f30341 /t/t5562-http-backend-content-length.sh
parenteebfe409628e337e283d57a870f52ae0d0e0de34 (diff)
downloadgit-574c513e8dda5598e9e08e8ca2a048bf120a5709.zip
git-574c513e8dda5598e9e08e8ca2a048bf120a5709.tar.gz
git-574c513e8dda5598e9e08e8ca2a048bf120a5709.tar.bz2
http-backend: allow empty CONTENT_LENGTH
According to RFC3875, empty environment variable is equivalent to unset, and for CONTENT_LENGTH it should mean zero body to read. However, unset CONTENT_LENGTH is also used for chunked encoding to indicate reading until EOF. At least, the test "large fetch-pack requests can be split across POSTs" from t5551 starts faliing, if unset or empty CONTENT_LENGTH is treated as zero length body. So keep the existing behavior as much as possible. Add a test for the case. Reported-By: Jelmer Vernooij <jelmer@jelmer.uk> Signed-off-by: Max Kirillov <max@max630.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t5562-http-backend-content-length.sh')
-rwxr-xr-xt/t5562-http-backend-content-length.sh11
1 files changed, 11 insertions, 0 deletions
diff --git a/t/t5562-http-backend-content-length.sh b/t/t5562-http-backend-content-length.sh
index 43570ce..f94d01f 100755
--- a/t/t5562-http-backend-content-length.sh
+++ b/t/t5562-http-backend-content-length.sh
@@ -153,4 +153,15 @@ test_expect_success 'CONTENT_LENGTH overflow ssite_t' '
grep "fatal:.*CONTENT_LENGTH" err
'
+test_expect_success 'empty CONTENT_LENGTH' '
+ env \
+ QUERY_STRING=/repo.git/HEAD \
+ PATH_TRANSLATED="$PWD"/.git/HEAD \
+ GIT_HTTP_EXPORT_ALL=TRUE \
+ REQUEST_METHOD=GET \
+ CONTENT_LENGTH="" \
+ git http-backend <empty_body >act.out 2>act.err &&
+ verify_http_result "200 OK"
+'
+
test_done