How to allow web service use different port?

[BarankinBeAMan]

My web site is deployed on port other than 80.
Now third party SOAPs fail as they use port 80.
Is there any way to allow them to use other port??

[mendhak]

Can't you just tell them to specify the port number in the URL?

Something like

http://sitename.com:88/Foldername/abc.asmx

[BarankinBeAMan]

No, this guy
http://www.xmethods.net/sd/2001/Curr...geService.wsdl
Will not do it just for me.

[mendhak]

In that case, did you try:

http://www.xmethods.net:80/sd/2001/C...geService.wsdl

?

[BarankinBeAMan]

Sure, that is what works, default port 80, or no port if you like.
If my web site is on other port, 801 for instance, the web service will not work.

[nemaroller]

If you define a web service to run on say port 8085, then any remote machine attempting to connect to that web service must use port 8085. AFAIK, IIS , and probably any web server, do not 'map' ports.

Therefore your website can only communicate with remote web services on the ports they specify available. Wouldn't make sense for you to dictate by the request what port the server should communicate to you with. The server defines that, and you either abide or you don't get access.

As far as your website running on a port other than port 80, my question is how does that affect retrieving data from a webservice on a seperate port?

Although your end user is using say port 8085, your web application can still communicate on other ports to remote services (that aren't the end user).