I'm totally new to SSL. I have .NET client that connect to Web Server (SOAP-based web Services) using HTTPS. Do I need to do anything extra at the .NET client app? Current, the server end-point URL that I use is already HTTPS, and it seems to work fine. However, when comparing to browser, a browser knows when it's HTTPS connection (the pad lock at address bar). So, how do I ensure that my .NET client is connect via HTTPS connection? Thanks in advance.
Related
I have recently hosted my .NET Core WebSocket server on Azure but I can't communicate with it from any client at all.
I used to host it locally on "wss://127.0.0.1:8080" using a self signed ssl certificate and everything worked fine, I also hosted it using SAP Hana Cockpit (uses Cloud Foundry api) and it worked if started on "http://0.0.0.0:8080", and I accessed both via "wss://ADDRESSWITHOUTPORT" from my angular client and both work fine.
When I host it on Azure and try to use it from client, it gives me Unexpected Response Message 200 (WebSockets don't even have that error, iirc), changing port/address/protocol doesn't seem to do anything at all.
What should I do?
If it's useful, this is my project https://github.com/JamesMaloney/WebSocketServer.NET
Thanks in advance, Giacomo
I have a local c# server running and listening on localhost and a browser connecting to a cloud service running a JavaScript HTML5 implementation of websockets. Standard ws://
This works great over HTTP:// and I can read the header and use it, but I need it to run in HTTPS:// I understand that I have to change to wss:// and this does connect to my server but the header is garbled/encrypted.
I have looked into SslStream but drawn a blank.
How do I handle this WebSocket Secure header in C#?
This question was answered in the comments:
If your app is behind a Proxy load balancer, it would normally manage the SSL for you (accessing your app without encryption).
If you need to manage SSL, complete the SSL handshake first (usually right after you accept the connection) and than parse protocol specific data (HTTP, Websockets, SMTP etc').
I'm trying to build an application that would use TCP sockets to communicate with a server.
When a proxy is detected in system settings, the application tries to connect through it through these steps:
Connect to proxy.
Issue CONNECT Host:Port HTTP/1.1<CR><LF>
Issue <CR><LF>
However it turns out that the proxy also needs to do NTLM authentication using the credentials of current user who's logged in.
.Net already implement this using:
Webproxy.crendentials = CredentialCache.GetDefaultCrendentials
But it only works with WebRequests types of sockets. And I am using regular sockets with Stream.Read and Stream.Write
I want to integrate an API that will allow my application to send requests to a web server. Unfortunately, this API is not well documented, and I have not gotten a reply from the person who supports the web service that released the API. The instructions on how to integrate the API are the following:
All API calls connect to the standard SSL port, and must begin with
https://www.websitename.com/api.php?username=username&password=password&,
followed by the list of parameters expressed as parametername=value&
I am new to C# development. Can you interpret this set of instructions and tell me how I'd go about integrating this API? I mainly am confused about connecting to the SSL port.
This sounds like it's just an HTTP request to that particular URL. You want to use the WebClient class, and possibly call the DownloadString method, depending on what the response contains.
The standard SSL port is 443, but if you're using a library that parses URLs correctly, it will connect to that port automatically if it sees https:// at the beginning. You can use a custom port by providing it after the hostname (separated by a :), such as https://websitename.com:8443/, if you had an SSL service running on port 8443 instead of 443.
I have setup a vanilla .net remote endpoint. It is behind a load balancer that handles SSL traffic so all the server side endpoint sees is plain old TCP traffic. The client configuration needs to be set up to connect to the load balancer over SSL.
The whole point of this exercise is to remove IIS from the technology stack.
What should the client configuration be? or is this even possible?