[
https://issues.apache.org/jira/browse/ASYNCWEB-37?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sangjin Lee closed ASYNCWEB-37.
-------------------------------
Resolution: Fixed
Fix Version/s: client-1.0.0
The fix has been checked in.
> connections with connection: close header should not be cached
> --------------------------------------------------------------
>
> Key: ASYNCWEB-37
> URL: https://issues.apache.org/jira/browse/ASYNCWEB-37
> Project: Asyncweb
> Issue Type: Bug
> Components: Client
> Affects Versions: client-1.0.0
> Reporter: Sangjin Lee
> Assignee: Sangjin Lee
> Priority: Minor
> Fix For: client-1.0.0
>
>
> If the keep-alive option is enabled, the server still can reply with a
> response with "Connection: close". In this case, the connection may be
> closed at any moment. However, today these connections are cached in the
> session cache. Depending on the timing, a possibility exists where a client
> may grab this connection and encounter random errors when the session finally
> gets closed.
> The connection should not be cached if the response has "Connection: close".
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
