Comment Feed for Restrict Web Service Access to host only (TechOff on Channel 9)

Re: Restrict Web Service Access to host only

Minh — Fri, 04 May 2007 20:33:23 GMT

m1keread wrote:

Minh wrote:

m1keread wrote: So if I read you correctly, I can go into IIS Manager and restrict the sites that can call the web service. If this is correct, it is a much more elegant way of doing what I need to do.

That should work.

Also, if I understood you correctly,

HttpContext.Current.Request.UserHostAddress

should be the IP of the web site, not the client's browser -- because it is the website that is making the web service request to your web service.

Thanks Minh,

What you said is what I understood also, however the IP address being returned was not the IP address of the physical Server hosting the website. I assumed that it was the IP address of my client PC on the internet. The Web server physical machine had a static IP address and yet the above line was returning different addresses at varying times. (I should have done some more research into it, but did not).

regards

Mike

Weird.... Just so I'm clear, you're querying the UserHostAddress from within the Web Service's code & not the Web site's code.

As ScanIam said, multiple NIC's could produce a differnt IP address, but it should be consistent, shouldn't it?

Well, maybe that's where the Firewall / router plays a role.

Re: Restrict Web Service Access to host only

ScanIAm — Fri, 04 May 2007 18:35:36 GMT

If you have 2 NIC cards or if the request comes through a firewall/NAT you'll get weird IP addresses.

Re: Restrict Web Service Access to host only

m1keread — Fri, 04 May 2007 09:00:37 GMT

Minh wrote:

m1keread wrote: So if I read you correctly, I can go into IIS Manager and restrict the sites that can call the web service. If this is correct, it is a much more elegant way of doing what I need to do.

That should work.

Also, if I understood you correctly,

HttpContext.Current.Request.UserHostAddress

should be the IP of the web site, not the client's browser -- because it is the website that is making the web service request to your web service.

Thanks Minh,

What you said is what I understood also, however the IP address being returned was not the IP address of the physical Server hosting the website. I assumed that it was the IP address of my client PC on the internet. The Web server physical machine had a static IP address and yet the above line was returning different addresses at varying times. (I should have done some more research into it, but did not).

regards

Mike

Re: Restrict Web Service Access to host only

Minh — Thu, 03 May 2007 20:35:37 GMT

m1keread wrote:

So if I read you correctly, I can go into IIS Manager and restrict the sites that can call the web service. If this is correct, it is a much more elegant way of doing what I need to do.

That should work.

Also, if I understood you correctly,

HttpContext.Current.Request.UserHostAddress

should be the IP of the web site, not the client's browser -- because it is the website that is making the web service request to your web service.

Re: Restrict Web Service Access to host only

m1keread — Thu, 03 May 2007 14:36:30 GMT

Thanks buddy,

The Web Services is a properly defined Web service and lives already in a .asmx file.

So if I read you correctly, I can go into IIS Manager and restrict the sites that can call the web service. If this is correct, it is a much more elegant way of doing what I need to do.

Thanks

Mike

Re: Restrict Web Service Access to host only

PerfectPhase — Thu, 03 May 2007 12:58:04 GMT

Why not move the webMethod into it's own asmx file and set IP restriction on the file via IIS admin tool?