Replies: 1 comment
-
Interesting observation. While my experience with Go's http library is limited and could not give a conclusive explanation, I would suggest the following steps to take to investigate.
Usually if you can observe the TLS handshake being completed correctly (and not followed by secured renegotiation), uTLS's job is done and the problem is more likely in how you used the HTTP libraries. One last thing to note, that |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm woefully under educated on golang, so forgive me as I learn and tinker.
I'd like to learn how uTLS works in order to integrate it in other projects. My first step is to take and test a few snippets of bare minimum code from examples.go, starting with the HttpGetDefault function. I'd like to run a simple GET request to different websites, examine the client hello on wireshark, and move on from there. I've commented out lines with the endpoints to test
requestHostname
andrequestAddr
and added my own below it. Commenting/uncommenting those and running a quickgo run .
returns an expected HTTP response code (302, 404 etc) when using the default endpoint of facebook.com or even testing against google.com.WHAT IS EXPECTED: When modifying the values hardcoded in
requestHostname
andrequestAddr
I should get an http response with at least something like 302, 200, or 404.PROBLEM: However, I get the following error when switching that to other websites:
#> HttpGetDefault failed: unexpected EOF
When changing the
var requestHostname
to a different address, it returns an EOF. I've searched everywhere I could but keep reading suggestions to usehttp.Close() = true
but this also doesn't seem to work, or I don't understand where to place it. I think thedefer.tlsConn.Close()
performs this task but again I don't have a thorough enough understanding of this library yet.Full code:
Beta Was this translation helpful? Give feedback.
All reactions