[ 
https://issues.apache.org/jira/browse/HTTPCLIENT-1981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16814682#comment-16814682
 ] 

ASF subversion and git services commented on HTTPCLIENT-1981:
-------------------------------------------------------------

Commit 63a6bd760ec1ec1f8daa6faf5a669aee3da3a06e in httpcomponents-client's 
branch refs/heads/HTTPCLIENT-1981 from Jay Modi
[ https://gitbox.apache.org/repos/asf?p=httpcomponents-client.git;h=63a6bd7 ]

HTTPCLIENT-1981: disallow TRACE requests with an enclosed entity


> HttpTrace should not accept an entity
> -------------------------------------
>
>                 Key: HTTPCLIENT-1981
>                 URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1981
>             Project: HttpComponents HttpClient
>          Issue Type: Bug
>    Affects Versions: 5.0 Beta3
>            Reporter: Jay Modi
>            Priority: Major
>         Attachments: http_trace_no_entity.diff
>
>
> The HttpTrace class allows a user to set an entity, but both RFC 2616 and RFC 
> 7231 state that the client MUST NOT send an entity/message body. I've 
> attached a patch that throws an UnsupportedOperationException for trace 
> requests in two places but maybe there is a better place/way to handle this.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to