Ticket #1104 (new defect)

Opened 1 year ago

Chunked transfer encoding not supported in request message

Reported by: Alexander Staubo <alex@purefiction.net> Assigned to: jan
Priority: normal Milestone:
Component: core Version: 1.4.11
Severity: major Keywords: chunked, transfer encoding, header, entity body, message, request
Cc: Blocking:
Need Feedback:

Description

Section 3.6 of the HTTP 1.1 spec specifies, albeit indirectly, that the Transfer-Encoding header applies to all HTTP messages, not only responses:

A server which receives an entity-body with a transfer-coding it does not understand SHOULD return 501 (Unimplemented), and close the connection. A server MUST NOT send transfer-codings to an HTTP/1.0 client.

Lighttpd, as far as I can tell, does not support requests with a chunked transfer encoding, which would be desirable when sending multipart messages. Also, if you specify the chunked coding and omit the Content-Length header, Lighttpd will return a 411 error.

Attachments


Add/Change #1104 (Chunked transfer encoding not supported in request message)




Change Properties