Home/ Questions/Q 509669
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-13T07:02:04+00:00

I have a web service that is on an internal server. It can be

  • 0

I have a web service that is on an internal server. It can be called from any website on our network.

More and more developers are starting to use it. Current probably 20+ pages use this service, and the number is growing fast. I can see a year from now, someone asking what pages are using this service and what methods.

I would like to log the url of the pages that use my web service as the request come in.
It would also be nice to know the method they are calling.I need to do something in such a way, that it does not affect the client web sites.My first thought was that I could write some code in the global.asax.

I have added some code to the Application_BeginRequest to log the request object details, but there does not appear to be anything about the requesting url.

What am I missing? Should I be looking at a different object?

Thanks.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    @David Stratton

    Thanks for your help. I think your suggestions were great. I accually did something very different, after your answer gave me some new ideas.

    I should have mentioned that I was generating the web proxy that most of my users were using to make calls against my web service. My client in general do NOT use the proxy that Visual Studio creates.

    Here is what did:

    I generated my web proxy client again, and added calls to log the httpcontext of the client before every call. Because the proxy is running on the client, he had access to everything I needed. That allowed me to record everything about the client and the specific call they were making. I realize this would not work for most cases. But all of my clients are internal web sites.

    It also had the advantage in that the clients did not have to modify their code at all. I just gave them all a new DLL. Problem solved. I get all the tracking data I want, and they did not have to modify their code.

    I was stuck trying to solve the problem from the web service’s point of view.

    I realize that there is still a whole in this implementation, because someone does not have to use my client proxy to call my service. I guess I could force that at some point in the future. For now, they could let Visual Studio genereate a web proxy for my service. However, if they do that I guess I don’t care. That is not the recommened way to call my service. I think the only one doing that is an ASP.NET 1.1 web site. When they upgrade, they will probably switch to my generated proxy.

    • 0