Review Board 1.7.16


http: Properly reject requests with Transfer-Encoding set

Review Request #3092 - Created Dec. 23, 2013 and submitted

David Lee
/team/dlee/ASTERISK-22486-reject-transfer-encoding
ASTERISK-22486
Reviewers
asterisk-dev
Asterisk
Asterisk does not support any of the transfer encodings specified in
HTTP/1.1, other than the default "identity" encoding.

According to RFC 2616:

   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.

This patch adds the 501 Unimplemented response, instead of the hard work
of actually implementing other recordings.

This behavior is especially problematic for Node.js clients, which use
chunked encoding by default.
HTTP requests using Node.js
Total:
2
Open:
0
Resolved:
2
Dropped:
0
Status:
From:
Description From Last Updated Status
Review request changed
Updated (Dec. 24, 2013, 10:41 a.m.)
  • changed from pending to submitted

https://reviewboard.asterisk.org/ runs on a server provided by Digium, Inc. and uses bandwidth donated to the open source Asterisk community by API Digital Communications in Huntsville, AL USA.
Please report problems with this site to asteriskteam@digium.com.