epilogue must not be forwarded in multipart/byteranges response
----------------------------------------------------------------
Key: HTTPCLIENT-846
URL: https://issues.apache.org/jira/browse/HTTPCLIENT-846
Project: HttpComponents HttpClient
Issue Type: Bug
Components: HttpClient
Affects Versions: 3.1 Final
Environment: Windows 2003
Reporter: Robin Gandhi
Priority: Critical
Fix For: 3.1 Final
Accoring to Http 1.1 specs Section "3.7.2 Multipart Types"---"the epilogue of
any multipart message MUST be
empty; HTTP applications MUST NOT transmit the epilogue (even if the original
multipart contains an epilogue). "
This is not being handled by HttpClient 3.1.
If the following response comes to Http Client it is not removing epilogue from
the response but accoring to the Http Specs HTTP applications MUST NOT transmit
the epilogue.
HTTP/1.1 206 Partial Content\r\n
Content-Type: multipart/byteranges; boundary=B-sqgssoeqmxnjprhluryj\r\n
Date: Wed, 10 Dec 2008 08:04:23 GMT\r\n
Connection: close\r\n
\r\n
\r\n
--B-sqgssoeqmxnjprhluryj\r\n
Content-Range: bytes 0-4/45\r\n
Connection: close\r\n
\r\n
body-\r\n
--B-sqgssoeqmxnjprhluryj\r\n
Content-Range: bytes 6-9/45\r\n
Connection: close\r\n
\r\n
gurl\r\n
--B-sqgssoeqmxnjprhluryj--\r\n
epilogue-7407030480\r\n
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
