Is it possible to implement web socket server client where clients are located on Windows C# form application and server is located on AWS cloud with a public ip to access via connection url and node.js?
Related
I have a .NET application that runs on Windows and am trying to send the application logs/structured logs (Serilog) through a proxy to a log server. The Windows machine doesn't have access to the Internet, so I was thinking that I could setup a Proxy(Squid) to forward logs to the Serilog log server (in AWS).
A web browser on the Windows machine can access the log servers' webpage/dashboard, however, the application itself isn't able to send logs through the Squid proxy server.
Questions:
Is a Proxy server the correct tool to use in this scenario?
Just because a web browser on the Windows machine (configured to use the Proxy), can access the log servers' URL, should that mean my application which is streaming serilog structured data, be able to send logs to this server?
Should I be routing my serilog data through the Proxy server, or should I be using a reverse proxy instead?
Here is how the serilog data is expected to travel:
Client application -->> Proxy Server -->> Corporate Domain Firewall -->> AWS
We have a web application that is required to run on HTTPS. We started to use a third party control that uses Websockets to connect to a windows service that will be running on the user computer. This page states that websockets should not be used in a mixed content environment. Is this security consideration still applies in this case (the websocket connection is not trying to connect to the same server that handled the https request)? If so, why would a websockets to a localhost would need to be secured? Isn't this just added complexity for no reason?
I have a tclhttpd server and I am trying to communicate it using secure server (SSL). When I start my server, I get a notification that:
httpd started on port xxxx
secure httpd started on SSL port yyyy
When I try to access the normal HTTP (http://localhost:xxxx), I can access the web folder. However, when I am trying to access the web server through a browser using secure port and https (https://localhost:yyyy) it shows:
The connection to localhost was interrupted while the page was loading.
I've also used the Httpd_SecureServer call to initialize the server but i still cannot connect using ssl.
What am I doing wrong here? any ideas?
I've to design a solution that permits to read real-time data generated by local sensors through a remotely-hosted web application.
The design is still work in progress: the sensors' data could be handled by a windows application/service installed on the client machine, or by some external hardware (like a raspberry) located on the same network of the client machine.
Now, I'm very new to WebSockets, but they seems exactly what I need for providing real-time data via browser.
My question is: can a remote web application open a WebSocket to a server that is located on the same local network which the client belongs to?
Is solution B possible? How can I achieve that?
For example, I'd like the server to be located on the client localhost. Sensors would send data to the local windows service, and the web application would show them by opening a WebSocket to localhost (client localhost, not server localhost!).
Well, I did some testing and the answer is yes, it is possible.
Test setup:
A web page hosted on a remote server, with a WebSocket client which connects to 'localhost'.
WebSocket server running on my pc.
It worked.
Web Api Service self hosted in Windows Service doesn't work with port forwarding, keeps saying connection actively refused. If you use the machine url directly works fine. If you use router url/port, which is port forwarded to web api service machine where selfhosting is taking place. The connection problem appears. To me this looks like the web api service can't recognize the port forwarding.