I am having problem connecting to websocket through IP Address. I can connect to websocket through WAN url "ws://dev.mysite.com/WSockets/WSHttpHandler.ashx". But unable to connect with LAN url "ws://192.168.1.23/MySite/WSockets/WSHttpHandler.ashx".
Error is "Error during WebSocket handshake: Unexpected response code: 500"
"http://dev.mysite.com" and "http://192.168.1.23/MySite" are the same as our site was hosted on own server (windows server 2012) IIS.
My Question is, is it possible to connect to websocket through server IP Address? If it can, what could be my problem?
Please help.
Thanks
The point that the websocket handshake protocol is actually HTTP. So, just like your virtual HTTP domain, your web server is set up to handle requests for dev.mysite.com differently from one for other domains.
Hence, your IP address is not equivalent to your domain name in a URL -- remember: A URL specifies a unique location, which means that domain names and IP addresses need not be exchangeable.
Related
I understand any client applications request queries with domain names will send to DNS server for domain name to IP resolution. But what if the requested queries is IP address only, does it mean the query will not send to DNS server for resolution? I'm wondering if the client applications will make the decision to save a trip to DNS server? Please advise. Thanks!!
Yes.if requested is IP address.client will direct connect to that IP.
You can test this by set wrong DNS server,the IP request still works.
IP address request only go through route.domain request will send DNS query then use answer IP to do request.
The website I want to go is pixiv.net, and after I ping it I found out it's ip, which is 210.129.120.44, but if I directly putting this ip as address in a browser, I got a access forbidden. But I can visit pixiv.net. And then I tried to bind this ip with pixiv.net in my host file. I can still get access to pixiv.net.
The web server at that location is probably configured to respond to a fully qualified domain name that it routes to a directory of HTML pages and other assets. It’s likely there is no configuration for requests to its root IP address.
It is likely one of the following two,
The nginx web server at that IP could be configured only to allow access via the domain name. prevent access via IP on nginx
The nginx server could be a reverse proxy which re-routes requests to the true web server. nginx as a reverse proxy server
I have installed IIS server on Windows 7 professional.
I am able to access the server using IP lets say 172.8.5.1 but when I try to ping the site outside of company network I get a network error (tcp_error)
Any one knows what needs to happen in order to access it over WWW?
Make sure that you have a static IP adresse,and then authorize incoming http request on port 80 from your router or your firewall.But the ip adresse should be accessible by internet
I have a oracle linux server and i am able to access the https of my local web directory WITHIN the linux server. But if i am trying to access it from the outside client PC https does not works.
Thanks.
If you can access it going to https://localhost and the browser doesn't give you an error that tells me the server is set up correctly and your certificate is valid.
There are several reasons why you wouldn't be able to access it externally. Are there iptables rules allowing inbound traffic over 443? Do external clients have a route to your server? Is there a firewall in the path, and is it allowing traffic over 443 to your oracle server?
How do you define not working? Are you getting connection refused? Is it timing out?
I want to host a site on local IIS 7.5 for internal testing. But I want people can access over the internet.
For this on my rackspace server, I have created an "A" record with subdomain.domainName.com and pointed my static IP address to it.
In IIS I have created a self-signed certificated with *.domainname.com that it can be used to multiple sites.
Now, i have published a site to a local directory and in IIS I have created a site with host name the same domain for which I have created an "A" record.
I have added http and https bindings with port 80 and 443 with the same host name.
But still my site is not working.
The error I am getting is "This webpage is not available"
Can any one help me?
Resolved it my self.
I was missing Port Forwarding in my router software for HTTPS.
In my web-application, each HTTP request is automatically be converted to HTTPS. And I forgot to forward Port 443's request to the machine to which I have set the static IP Address and DNS.
After adding that port forwarding record to the router's software my application is working fine over internet.