David Steele 3bdba4933d Fix incorrect handling of transfer-encoding response to HEAD request. ...

The HTTP server can use either content-length or transfer-encoding to indicate that there is content in the response.  HEAD requests do not include content but return all the same headers as GET.  In the HEAD case we were ignoring content-length but not transfer-encoding which led to unexpected eof errors on AWS S3.  Our test server, minio, uses content-length so this was not caught in integration testing.

Ignore all content for HEAD requests (no matter how it is reported) and add a unit test for transfer-encoding to prevent a regression.

Found by Pavel Suderevsky.

2019-07-17 16:49:42 -04:00

..

common

Add testUser() and testGroup().

2019-05-13 07:51:11 -04:00

module

Fix incorrect handling of transfer-encoding response to HEAD request.

2019-07-17 16:49:42 -04:00

test.c

Ignore SIGPIPE signals and check EPIPE result instead.

2019-01-06 17:42:44 +02:00

valgrind.suppress

Add storageInfoList() to get detailed info about all entries in a path.

2019-04-23 19:33:55 -04:00