[ https://issues.apache.org/jira/browse/TS-2902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14102426#comment-14102426 ]
ASF subversion and git services commented on TS-2902: ----------------------------------------------------- Commit db3de1894901d4ec9e2bc7983dac48941b104ffc in trafficserver's branch refs/heads/master from [~maskit] [ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=db3de18 ] TS-2902: Allow POST requests without a Content-Length header > Allow POST requests without a Content-Length header > --------------------------------------------------- > > Key: TS-2902 > URL: https://issues.apache.org/jira/browse/TS-2902 > Project: Traffic Server > Issue Type: Improvement > Reporter: Masakazu Kitajo > Assignee: Bryan Call > Labels: review > Fix For: 5.1.0 > > Attachments: make_it_configuarable.patch > > > I get "*400* Content Length Required" when user agents send a POST request > that doesn't contain any body data without a Content-Length header. > (The header is omitted because the length is zero, I think) > According to RFC2730 Section 3.3.2, presence of Content-Length is not MUST. > http://tools.ietf.org/html/rfc7230#section-3.3.2 > {quote} > A user agent SHOULD send a Content-Length in a request message when > no Transfer-Encoding is sent and the request method defines a meaning > for an enclosed payload body. > {quote} > Also according to section 3.3.3, a server are allowed to reject similar > request with 411 Length Required, but not *400*. > http://tools.ietf.org/html/rfc7230#section-3.3.2 > {quote} > A server MAY reject a request that contains a message body but not a > Content-Length by responding with 411 (Length Required). > {quote} > Traffic Server should accept the requests, no body data without > Content-Length header, or reject it with *411*. I think the former one is > better for interoperability. -- This message was sent by Atlassian JIRA (v6.2#6252)