[
https://issues.apache.org/jira/browse/HTTPCLIENT-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12856424#action_12856424
]
Ortwin Glück commented on HTTPCLIENT-427:
-----------------------------------------
Jon,
You are *not* implementing a proxy! Only a cache. A proxy is an intermediate
server that the client is fully aware of. The client uses the CONNECT method
and proxy-specific headers to interact with a proxy. A cache however is fully
transparent to the client. The client has no knowledge about the proxy. No Via
headers. No Max-Forwards interpretation. A cache only interacts with the
headers that control lifetime of the cached object. Apart from that it just
replays responses to the client. That implies that you have to store also the
original headers and not just the request body. In my opinion the cache should
even issue the original Date and Server headers back to the client and not
generate new ones.
> Implement a cache to perform real request only when needed
> ----------------------------------------------------------
>
> Key: HTTPCLIENT-427
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-427
> Project: HttpComponents HttpClient
> Issue Type: Improvement
> Components: HttpClient
> Environment: Operating System: Linux
> Platform: PC
> Reporter: Marc Guillemot
> Priority: Minor
> Fix For: Future
>
>
> Browsers may cache received content according to the values of different
> response headers. It would be great if HttpClient could do the same.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://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]
