I am working on a site that exposes a set of webservices within a folder in the site:
services
--- servicea.asmx
--- serviceb.asmx
These services are set up to allow some interoperability with other sites that we control, and these all reside on the same server.
The site uses asp.net forms based authentication, but the services folder has been exempted from this and each service performs it's own authentication when calling a method, and checks that he access is from a local address only, and this works fine.
However, if I access services/servicea.asmx from an external address, I can still see a list of the methods available. I cannot effectively call any of these methods from an external address, which is as it should be, but I'm not comfortable exposing our internal API like this. Is there any way to stop an asmx file from responding with a list of methods when accessed outside the box?