![]() There might be some clues available if you use Wireshark to record this traffic, filter that for tls, and look at the client & server handshakes to check which versions are offered in the failing handshake.Īre there any errors shown in HTTP Toolkit at all? If you enable the error filter (start typing 'errored' into the filter box on the View page, and pick the error filter option that appears) then it will show only requests that couldn't be properly sent, due to either upstream or downstream issues. ![]() Happy to investigate if you can confirm the versions involved though so I can try to reproduce this. I'm not sure what the limits are there, or if we can change them. If it's a downstream error, I suspect this means that the client on iOS is trying to use some very old TLS protocol that isn't properly supported. When this fails, does a failing request show up in HTTP Toolkit itself, with the above error as the response body? That should be definitive: if a full request wit this error appears then it's definitely an upstream error, if not (there might be a blank 'connection reset' line shown in HTTP Toolkit instead) then it must be a downstream error. I'm not totally sure how to interpret it - it's not totally clear whether this is an error in accepting a client TLS connection to HTTP Toolkit, or the TLS connection from HTTP Toolkit upstream. This error comes directly from OpenSSL somewhere. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |