![]() Imo non-localhost self-signed certificates is an advanced use case, which fairly cleanly draws a line between simple/hobbyist usage and professional/enterprise cases. Unfortunately for unrelated reasons editing the raw error responses like this to inject extra text is a little more complicated, but I'll definitely look into it as a next step. Or is self-signed certs on non-localhost a PRO-only feature? Which is fine, I guess, I as long as I know about it and there is the localhost portforward workaround. The export NODE_TLS_REJECT_UNAUTHORIZED=0 workaround (or some other workaround) would work again. I was looking for the version so I could post the version in my github post above! :-) Mind if I ask why you're looking for it? I was looking for the version, but apparently that isn't visible in the GUI. I'd love to give more features away for free But without that, had there been even more info in HTTP Toolkit, I personally may not have even seen/found it. A tiny bit of extra information in the browser, even "(Take a look at the HTTP Toolkit GUI for more.)" would be enough. When I accessed the page, I was looking at the browser, so I was expecting any additional information to be there, in the browser. Mind if I ask why you're looking for it?įYI: I didn't even think to look in the HTTP Toolkit GUI. Hovering over the logo isn't really discoverable, but it shouldn't be something you need often. I think that 4.0.0 version file you found is actually the internal Electron version. You can see the version by hovering over the HTTP Toolkit logo in the top left. Happy to debate on the details, but so far it feels reasonable to me, and it's slowly moving the project towards sustainability. My current strategy is basically to ensure all essential features are freely available, and a limited set of features you'd only need for serious professional development or extensive use are paid. I'd love to give more features away for free, but the project needs to be sustainable somehow. The PRO config page was available for non-PRO versions Should be live within the next few hours □ yada yada yada.įortunately I'm working on exactly that as we speak: the Error: certificate has expired text was a link to a page describing the localhost thing and that Pro can. But so far I can't see any client's certificate.E.g. What I need is to access client's certificate on a server side to do proper authentication. ![]() * SSL certificate verify result: self signed certificate (18), continuing anyway.Īs you can see SSL negotiation is in place and curl client successfully reports server certificate. * SSL connection using TLSv1.2 / ECDHE-ECDSA-AES128-GCM-SHA256 * TLSv1.2 (IN), TLS handshake, Finished (20): * TLSv1.2 (IN), TLS change cipher, Client hello (1): * TLSv1.2 (OUT), TLS handshake, Finished (20): * TLSv1.2 (OUT), TLS change cipher, Client hello (1): * TLSv1.2 (OUT), TLS handshake, Client key exchange (16): * TLSv1.2 (IN), TLS handshake, Server finished (14): * TLSv1.2 (IN), TLS handshake, Server key exchange (12): * TLSv1.2 (IN), TLS handshake, Certificate (11): * TLSv1.2 (IN), TLS handshake, Server hello (2): * TLSv1.2 (OUT), TLS handshake, Client hello (1): * TLSv1.2 (OUT), TLS header, Certificate Status (22): * CAfile: /opt/local/share/curl/curl-ca-bundle.crt * Cipher selection: successfully set certificate verify locations: While if I invoke curl call to a server providing my certificates, then I can see server certificates: curl -L -k -key mykey.key -cert mycert.pem -vvv * Trying 127.0.0.1. Here is a server code: package mainįunc defaultHandler(w http.ResponseWriter, r *http.Request) ːiSZ]Īs you can see the client's certificates are empty. I'm trying to understand how to get client's certificates in Go web server.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |