Referrer or HTTP_REFERER

Can any one suggest alternative to capture the URL of the
Web services consumer in Web service. For VS.Net 2003,
HttpContext.Current.Request.UrlReferrer or
HttpContext.Current.Request.ServerVariables
("HTTP_REFERER") both holds null value. Any Patch/Fixes
available?

re: Referrer or HTTP_REFERER

In article <1774d01c4497e$5d29e470$a601280a@phx.gbl>,
kokateshirish@hotmail.com says...[color=blue]
> Can any one suggest alternative to capture the URL of the
> Web services consumer in Web service. For VS.Net 2003,
> HttpContext.Current.Request.UrlReferrer or
> HttpContext.Current.Request.ServerVariables
> ("HTTP_REFERER") both holds null value. Any Patch/Fixes
> available?[/color]

How would that work? A webservice is something that is called directly.
I don't know how you can set up something to "refer" to a webservice and
have it execute properly.

--
Patrick Steele
Microsoft .NET MVP
http://weblogs.asp.net/psteele

re: Referrer or HTTP_REFERER

Obviously! Web services are consumed directly
and 'HTTP_REFERER' was mentioned for elaboration.

Alternatively, by capturing URL of the consumer one can
restrict and monitor web services consumers.

Shirish[color=blue]
>-----Original Message-----
>In article <1774d01c4497e$5d29e470$a601280a@phx.gbl>,
>kokateshirish@hotmail.com says...[color=green]
>> Can any one suggest alternative to capture the URL of[/color][/color]
the[color=blue][color=green]
>> Web services consumer in Web service. For VS.Net 2003,
>> HttpContext.Current.Request.UrlReferrer or
>> HttpContext.Current.Request.ServerVariables
>> ("HTTP_REFERER") both holds null value. Any[/color][/color]
Patch/Fixes[color=blue][color=green]
>> available?[/color]
>
>How would that work? A webservice is something that is[/color]
called directly.[color=blue]
>I don't know how you can set up something to "refer" to[/color]
a webservice and[color=blue]
>have it execute properly.
>
>--
>Patrick Steele
>Microsoft .NET MVP
>http://weblogs.asp.net/psteele
>.
>[/color]

re: Referrer or HTTP_REFERER

In article <1ec901c44a42$d2b12c20$3501280a@phx.gbl>,
kokateshirish@hotmail.com says...[color=blue]
> Alternatively, by capturing URL of the consumer one can
> restrict and monitor web services consumers.[/color]

But the consumer is not a URL, they're just an IP address. And if
they're behind a proxy, the same IP address could be used by numerous
consumers.

--
Patrick Steele
Microsoft .NET MVP
http://weblogs.asp.net/psteele