Sounds like maybe you are trying to access the server by an IP address
rather than a DNS name? I believe the TLS handshake will fail in this case
since it tries to match the host name to the subject name on the
certificate or a SAN on the certificate. If you can arrange for DNS or the
local resolver to point to the host with a name matching the name on the
certificate, that should work.
Thanks,
Carl Waldbieser
On Tue, Oct 17, 2017 at 3:36 AM, Ohad Shai
Hi,
I have an important question about twisted HTTPS client-server communication.
I ran an HTTPS server with my own certs and tried to communicate with a twisted HTTPS client with the specific cert.
I am getting an error that says: "Invalid DNS-ID".
all the error info with all my code is in here: https://gist.github.com/ anonymous/e46d4d8dc1c102857497cde9e2fc4725#file-gistfile1-txt Twisted-HTTPS-client-server https://gist.github.com/anonymous/e46d4d8dc1c102857497cde9e2fc4725#file-gist... gist.github.com Twisted-HTTPS-client-server
I will be appreciate if someone has a clue how can I fix this error.
Thanks,
*Ohad Shai* Software Engineer, EDR Linux 972-052-6887792 ohad.shai@cyberbit.com
_______________________________________________ Twisted-web mailing list Twisted-web@twistedmatrix.com https://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-web