[
https://issues.apache.org/jira/browse/HTTPCLIENT-2277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17728135#comment-17728135
]
Arturo Bernal commented on HTTPCLIENT-2277:
-------------------------------------------
AFAIK the Apache HttpComponents library does not inherently support storing
incomplete responses or combining partial content in the caching mechanism,
h3. [3.3. |https://www.rfc-editor.org/rfc/rfc9111#section-3.3] [Storing
Incomplete
Responses|https://www.rfc-editor.org/rfc/rfc9111#name-storing-incomplete-response]
* *Storing Incomplete Responses:* Apache HttpClient, at that time, didn't have
built-in mechanisms to identify and store incomplete responses. In general, if
an HTTP response is received and it is not flagged with an error status (like
HTTP 206 Partial Content), it is treated as a complete response
h3. [3.4. |https://www.rfc-editor.org/rfc/rfc9111#section-3.4] [Combining
Partial
Content|https://www.rfc-editor.org/rfc/rfc9111#name-combining-partial-content]
* *Combining Partial Content:* Similarly, Apache HttpClient doesn't inherently
support the combining of partial content. The library is typically used to
issue HTTP requests and process HTTP responses. How partial content is handled
is usually a higher-level concern, not something that HttpClient manages itself.
> HttpClient Cache conformance to RFC 9111
> ----------------------------------------
>
> Key: HTTPCLIENT-2277
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-2277
> Project: HttpComponents HttpClient
> Issue Type: Improvement
> Components: HttpCache
> Reporter: Oleg Kalnichevski
> Priority: Major
>
> Ensure HttpClient Cache conforms to RFC 9111.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org
For additional commands, e-mail: dev-h...@hc.apache.org
