[
https://issues.apache.org/jira/browse/HTTPCLIENT-801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12639069#action_12639069
]
Ortwin Glück commented on HTTPCLIENT-801:
-----------------------------------------
The question however remains how useful this behaviour is. From a TCP packet
point of view it makes the most sense to limit the chunk size. If your MTU is
1480 bytes, you don't want a chunk of 1481, as this would create an extra
1-byte payload packet.
> Having problems with ChunkedOutputStream
> -----------------------------------------
>
> Key: HTTPCLIENT-801
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-801
> Project: HttpComponents HttpClient
> Issue Type: Bug
> Components: HttpClient
> Affects Versions: 3.1 Final
> Reporter: ozgur alkaner
> Original Estimate: 4h
> Remaining Estimate: 4h
>
> Sorry if i am wrong about this. But i am confused by the way
> ChunkedOutputStream is implemented.
> This is what is written at the begining of the ChunkedOutputStream.java :
> "Chunks are guaranteed to be at least as large as the buffer size (except for
> the last chunk)."
> I see that the code is implemented as mentioned above, However does that
> comply with the http chunking in http1.1?
> Shouldn't that be
> "Chunks are guaranteed to be at most as large as the buffer size (except for
> the last chunk)."
> The default size for the chunk cache seems to be 2048 , however when i set
> the post request body to be larger than this value say 5000,
> ChunkedOutputstream creates a single chunk of size 5000.
> I will be pleased if you can comment on this?
> Ozgur
--
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]
