I have a mobile webserver, which is connected to internet through GPRS. ISP only provide a private IP, so is not possible to access to it using something like no-ip or dyndns. Is there a way to use a proxy server to access to this mobile webserver?:
Mobile webserver stablish connection with proxy server
a web browser (client) stablish a connection with the proxy server, and redirect the stablished socket directly to mobile webserver
I need to have several of these type of mobile web server (each with a different hostname) connected to a proxy server (ie. its domain is myproxy.com), and provides to a normal user a web site in mobileserverlist.myproxy.com with a list of links, each link will point to ie
http://mobilewebserver1.myproxy.com
http://mobilewebserver2.myproxy.com
http://mobilewebserver3.myproxy.com
here the proxy server will redirect traffic to each mobile web server (all of them in private networks)
ideas?
You mean you have for example a mobilephone as a web server. You can't get a static ip adress and even no dyndns domain. That you can't get dyndns domain is surprising. But you dont really need a proxy. You can easily set up a request script, that direct your users to the location you want.
Related
I have two Azure Web App Services: front-end (written on Angular) and back-end (written in C# with SignalR). Either of them is placed on its own server, and I am trying to make front-end connect to back-end. Previously everything worked locally when I ran it on localhost, with http, but when I try to do the exact same thing on Azure (I replaced localhost with azure website domains), I get this error in Chrome:
I see that https is replaced by 'wss', which I guess is not fine for SignalR (because it's supposed to fall back to https/https if wss/ws is unavailable, as one of the commenters stated). So apparently my front-end can't see my backend.
What I've tried so far:
Changing protocols to http, the way it was with localhost
Setting backend to listening to 0.0.0.0:5000
Turning on Web Sockets in Azure settings (on both client and server)
What is my problem, and how do I connect my client side to the server side? Thanks.
You should not use port 5000 on App Service. Configure your app so that it only uses the default ports when deployed (effectively port 80 and 443). WSS/SignalR works fine over these default ports.
You can also see the list of exposed ports.
I am developing hotspot helper application which tries to connect to the captive network after connecting to it, I need to handle the authentication within the app.
Approach 1
I used NEHotspotConfigurationManager in order to programmatically connect to the WiFi network and it works great. The problem i am facing is after connecting to the captive network iOS does not send the request to the connected network until the connected network has internet access or I manually go to the settings and it pops up the web page for authentication and i click cancel and select use without internet.
Approach 2
Second approach i used is by using NEHotSpotHelper as described in this tutorial
In this approach when I receive the commandType authenticate it does not send request to the Wi-Fi network (If the device is connected to the 4g the request goes over it otherwise it returns internet connection appears to be offline)
So how can i authenticate the user from the app after connecting to the WiFi with limited access?
I found that developer need to bind the request with the received command before making web request to the connected network. All you need to do is to make NSMutableURLRequest and then call hitTestURLRequest.bind(to: command) because bind function is defined in the category of NSMutableURLRequest.
Related question: https://stackoverflow.com/a/50753526/1796092
I have deployed express REST full application which is listening on port xxxx in server A. Express Application is behind firewall due to security issues. Also have angular application deployed in another server B, which is NOT behind firewall and is accessing the express REST full API's deployed in server A. If i access Angular application from inside company network, application is able to get response from express REST full API's. But If i access Angular application from outside company network application is NOT able to get response from express REST full API's. What networking/firewall changes am supposed to do to get endpoints access from Angular application from outside company network also?? I have tried creating new inbound rules for port xxxx in firewall but not able to get working.
Iam able to access rails app in all systems with in network, but unable to access in mobiles.
I started app like below
rails s -b ip
Double check if your mobile is in the same network of your server. You can do this either by pinging your mobile device (if it support ping) or doing a network scan using tools like nmap or take a look at your router to see where is your device. If you want to allow all access, the binding ip should be 0.0.0.0.
We have a mobile website developed for a conference which should be accessible to users thru smartphone/tablet/laptop when they connect to a wifi router.
Is it possible to setup a xampp server on a local pc connected to the router and assign it a url, so that users can type the url and access the website?
Will the users have to type an ip address or would it be possible to assign a url?
I read in some posts that one way would be to setup a captive portal but we do not have the time & resources to setup a captive portal. Kindly correct me if I am wrong.
Thanks in advance,
Raghav
I feel like this could be possible by building out a DNS server for the lan. And entry for your webserver would then have to be in there. Then, in the router settings, specify the local DNS server as the DNS that gets assigned to other LAN computers via DHCP. Any node that connects to the router and uses DHCP to resolve IP settings should get that DNS server. Then when a client attempts to resolve www.website.com, it will ask the local DNS to resolve it and the request will be translated to the LAN address. I have never done this before but it may be worth a shot.