You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
phauer
changed the title
Connection to MockWebServer takes 5 seconds if "Expect: 100-continue" and "chunkedStreamingMode" is set
Connection to MockWebServer takes 5 seconds if "Expect: 100-continue" and "chunkedStreamingMode" are set
Mar 8, 2019
I'm using the MockWebServer as a simple S3 mock in my integration test. As the S3 SDK makes use of the Expect: 100-continue-Header too, this is an issue for me as well. It works, but tests are taking way more time than they'd normally need.
I am in the same situation as @andre161292. We have an internal library making use of the Expect: 100-continue header.
Out tests pass but they take much longer that they should.
Hi,
when an
HttpURLConnection
to a MockWebServer is configured withconnection.setRequestProperty("Expect", "100-continue")
andconnection.setChunkedStreamingMode(0);
(or any other number)the
connection.getOutputStream()
takes 5 seconds before it returns.I created a small test that reproduces this issue:
If you remove one or both configurations, the test is fast again.
You may wonder, why I set those headers. I have to use the tus-client-java library, which does this.
I hope, this can be fixed.
Kind Regards,
Philipp
The text was updated successfully, but these errors were encountered: