-
Notifications
You must be signed in to change notification settings - Fork 9.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
too many follow-up requests problem #3827
Comments
Can you provide a sample of the response headers you are sending with the 408? Or a reproduction test case? There is changed handling of 408 in 3.10, which has not yet been released. I don't think it fixes it however. #3753 But even if that doesn't help you can see examples in that PR of how to make a reproduction test case. Also relevant is a fix in August for 408 handling #3500 |
@yschimke
I'm not quite sure because we changed the status code but just status code and other things are remained so it should like the above (I copied the exact response from chrome, hope it's become useful) |
Fixed in 3.10. |
it still happens on version 3.14.9
|
@aleeee Check out this solution: https://stackoverflow.com/a/63512049/8026243 |
hello,
recording to this issue it looks like OkHttp has a problem with status code
408
.just want to put it here to be fixed.
The text was updated successfully, but these errors were encountered: