[ http://issues.apache.org/jira/browse/HTTPCORE-17?page=comments#action_12454708 ] Roland Weber commented on HTTPCORE-17: --------------------------------------
These headers MUST NOT exist. They are under direct control of the HTTP transport layer and apply only for a single hop. Proxies MUST NOT forward these headers, and applications MUST NOT set them. Simply forwarding those headers will most likely cause the HTTP transport to fail, because the content length is wrong or the transfer encoding used for the message entity is different from the one specified in the header. cheers, Roland > In RequestContent class, if one of the headers TRANSFER_ENCODING or > CONTENT_LEN already exist a ProtocolException is thrown. We removed the > exception because if one of these headers exists we want to do nothing, just > forward it as it is > -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: HTTPCORE-17 > URL: http://issues.apache.org/jira/browse/HTTPCORE-17 > Project: HttpComponents Core > Issue Type: New Feature > Components: HttpCore > Affects Versions: 4.0-alpha2 > Reporter: Flash Networks > Priority: Minor > Attachments: RequestContent.java > > > In RequestContent class, if one of the headers TRANSFER_ENCODING or > CONTENT_LEN already exist > a ProtocolException is thrown. We removed the exception because if one of > these headers exists we want to do > nothing, just forward it as it is -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
