[
https://issues.apache.org/jira/browse/HTTPCLIENT-2118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17206323#comment-17206323
]
Michael Osipov commented on HTTPCLIENT-2118:
--------------------------------------------
Wait a second, I have left out:
{noformat}
...
59 1.978067 52.216.114.219 192.168.11.3 TLSv1.2 450
Application Data
1914 8.027513 52.216.114.219 192.168.11.3 TLSv1.2 85
Encrypted Alert
1915 8.082430 192.168.11.3 52.216.114.219 TCP 54 49900 →
443 [ACK] Seq=1415 Ack=3827 Win=130560 Len=0
1949 10.061705 52.216.114.219 192.168.11.3 TCP 54 443 →
49900 [FIN, ACK] Seq=3827 Ack=1415 Win=32000 Len=0
1950 10.061798 192.168.11.3 52.216.114.219 TCP 54 49900 →
443 [ACK] Seq=1415 Ack=3828 Win=130560 Len=0
1951...
{noformat}
After the last communication, before we reuse the connection the server already
signals what he's going to close the connection we notice this, but react only
after the headers?
> Difference in behavior between 4.5.x and 5.0.x - CloseableHttpClient returns
> 403 after NoHttpResponseException
> --------------------------------------------------------------------------------------------------------------
>
> Key: HTTPCLIENT-2118
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-2118
> Project: HttpComponents HttpClient
> Issue Type: Bug
> Components: HttpClient (classic), HttpClient (Windows)
> Affects Versions: 5.0.2
> Environment: Microsoft Windows 10 version 2004 [10.0.19041.508]
> Oracle JDK 11.0.8
> Reporter: Michael Lee
> Priority: Major
> Attachments: all_except_wire.log, all_except_wire.setMaxTotal5.log,
> all_except_wire.setMaxTotal6.log, demo.zip, headers.log, test_output.txt,
> wireshark.pcapng
>
>
> My application reuses an instance of CloseableHttpClient to retrieve the
> content from a list of URLs. After upgrading HttpClient from 4.5.x to 5.0.2
> (also 5.0 and 5.0.1), it always gets a NoHttpResponseException followed by a
> response code of 403 for a particular URL in the list. When using 4.5.x, it
> always gets a 200 or 304 for that particular URL.
> The behavior may be different if the order of the URLs in the list is changed.
> To illustrate the problem, I have extracted code from my application into the
> sample Maven project attached. In the JUnit test, testHttpClient4() will get
> either 200 or 304 for all the URLs. On the other hand, testHttpClient5()
> always gets 403 for the last URL in the list. In this project, I
> intentionally added a If-Modified-Since header with the value being current
> time minus 1 minute so that we should get a 304 from most of the URLs.
> Can you investigate if this is really an obscure bug or an undocumented
> behavior change related to how CloseableHttpClient handles redirects?
> Thanks.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org
For additional commands, e-mail: dev-h...@hc.apache.org
