I have changed the port for a wcf service using edit biding in iis. Now the issue is that the url of service contains port number like https://localhost:8080/test.svc
How to hide the port number in service url like:https://localhost/test.svc
You can only do that if service runs on default port i.e. 443 for HTTPS or 80 for HTTP. Change port to 443 and then you can use it as https://localhost/test.svc
Related
I created a very basic express app which listens at port 3000 for HTTP, 4000 for HTTPS. I have static ip.
How can i use my domain to access my express app. ( Currently i can access via [external ip]:[port])
NOTE: I am using raspberry pi with raspbian OS.
Your app has to listen on port 80 for HTTP requests and port 443 for HTTPS requests.
Alternatively, you can use a proxy server like Nginx to handle HTTP and HTTPS, and you can configure your app to listen on any port. Also, don't forget to configure Nginx according to your app's ports.
I'm listening on to port 80 and 443 using the TCPListener in my .net application. This is windows service and not a web application therefore not hosted in the IIS as well.
I know there are many ways to redirect the request from http to https using the URL Rewrite in the IIS.
BUT, it there any clean way of redirecting all the incoming requests on port 80 to port 443. Basically I want to enforce a secure connection with the server.
Any help in this regard will be great.
Thanks
i have a server with two public IP, the first is used by IIS, the second IP is configured in Apche in Listen directive. But when i run Apache service i receive the error:
make_sock: could not bind to address <ip address>:80
All web sites in IIS are binding on first IP.
P.S. Sorry for my english
IIS lock all ip on port 80 (0.0.0.0:80).
I found this: Stop http.sys from listening on port 80 in Windows
you can use:
netsh http add iplisten ipaddress=127.0.0.1
This 'release' all ip (not 127.0.0.1) and Apache works!
I would like to know about the port enabling and port forwarding to make the sharepoint site collection out side the network.
Assume, i have created a web application on the port 3333.and my system is having static ip as well. Now how to enable this port and how to make the url as http : // server name instaed of http : //server name:3333
I am using a Silverlight application that has net.tcp WCF communications. I would like to self host the ClientAccessPolicy.xml within the ServiceHost and the policy file must be on the root, port 80, as per Silverlight net.tcp requirements (TCP port 4502-4534, etc.). My problem is that when my ServiceHost is running it steals port 80 root from IIS and none of my web pages work.
The code to create the policy endpoint looks like:
host.AddServiceEndpoint(typeof(IPolicyGetter), new WebHttpBinding(), "http://localhost/").Behaviors.Add(new WebHttpBehavior());
When the ServiceHost is running then I can see my http://127.0.0.1/ClientAccessPolicy.xml, but all web sites on port 80 stop working - I see the standard WCF "Endpoint not found" web page generated by the Endpoint. When I turn off the ServiceHost then I can see my web site but the ClientAccessPolicy.xml is gone.
I have tried using a complete path for the endpoint URI:
policyUri.Scheme = "http";
policyUri.Port = 80;
policyUri.Query = "ClientAccessPolicy.xml";
host.AddServiceEndpoint(typeof(IPolicyGetter), new WebHttpBinding(), policyUri.ToString()).Behaviors.Add(new WebHttpBehavior());
but this throws an argument exception. Moving the policy to a subdirectory or a different port will not work because Silverlight only looks at port 80 on the root web directory.
Obviously I can just copy the ClientAccessPolicy.xml into the web root directory and disable the policy endpoint. Is there a way to button-down the endpoint so that it only hijacks calls to ClientAccessPolicy.xml but does not steal the entire IIS port 80?
No, you cannot have two processes listening on the same TCP/IP port. If your ServiceHost is listening on port 80, then it is going to be the only process responding to connections on that port.
Having said that, you can have a "master" process listen on port 80 and redirect connections to "child" processes, but this is beyond the scope and intent of ServiceHost.