Skip to content
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

Connection with sockets #2

Closed
Ahn1 opened this issue Jul 22, 2013 · 1 comment
Closed

Connection with sockets #2

Ahn1 opened this issue Jul 22, 2013 · 1 comment
Assignees
Labels

Comments

@Ahn1
Copy link
Contributor

Ahn1 commented Jul 22, 2013

Hello,

i saw you created a own TLS/Sockets Implementation.

Is this necessary because windows phone does not really support https?

If this sould be true, i have to use this too...
I've used the default HttpWebRequest now.

@ghost ghost assigned framedynamic Jul 22, 2013
@framedynamic
Copy link
Contributor

That is not a full TLS implementation, it is only a handshake to fetch the certificate to show to the user as a feature.

The phone actually supports TLS but the HttpWebRequest class will reject a self signed certificate as non valid if the certificate is not in trusted storage or the issuer is non of the root ca's installed on the phone.

The class will fail with the insignificant message "Not found" but in fact rejects the server certificate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants