How to hide available web service function declares

[John K]

How do you hide the available functions (and syntax) that are normally
displayed when you browse to a webservice (e.g. httpx://xxx.com/CMgr.asmx)?

If you go to that page you will see a list of the available functions and
you can click on the function name to reveal the calling syntax. We need to
remove this documentation for security reasons. We do not want other people
to access the functions. We only want precompiled applications that know
what functions are available and the required calling syntax.

I tried a solution listed in an article at
http://www.15seconds.com/issue/040609.htm, but it did not work. It involved
adding a tag to the web.config file (<removename="Documentation"/> ).

Thank you.

[Rolando]

put a space between remove and name
John K wrote:

How do you hide the available functions (and syntax) that are normally
displayed when you browse to a webservice (e.g. httpx://xxx.com/CMgr.asmx)?

If you go to that page you will see a list of the available functions and
you can click on the function name to reveal the calling syntax. We need to
remove this documentation for security reasons. We do not want other people
to access the functions. We only want precompiled applications that know
what functions are available and the required calling syntax.

I tried a solution listed in an article at
http://www.15seconds.com/issue/040609.htm, but it did not work. It involved
adding a tag to the web.config file (<removename="Documentation"/> ).

Thank you.

[John K]

It seems to work, at least my application still works. After adding this tag
to hide the documentation; is it normal to see an error message when browsing
to the page. Here is the error I get when going to that page in Internet
Explorer on the same machine as the service:

An unhandled exception was generated during the execution of the current web
request. Information regarding the origin and location of the exception can
be identified using the exception stack trace below.

Stack Trace:
[InvalidOperationException: Request format is unrecognized.]

System.Web.Services.Protocols.WebServiceHandlerFac tory.CoreGetHandler(Type
type, HttpContext context, HttpRequest request, HttpResponse response) +491033

System.Web.Services.Protocols.WebServiceHandlerFac tory.GetHandler(HttpContext
context, String verb, String url, String filePath) +104
System.Web.HttpApplication.MapHttpHandler(HttpCont ext context, String
requestType, VirtualPath path, String pathTranslated, Boolean useAppConfig)
+175

System.Web.MapHandlerExecutionStep.System.Web.Http Application.IExecutionStep.Execute() +120
System.Web.HttpApplication.ExecuteStep(IExecutionS tep step, Boolean&
completedSynchronously) +155


--------------------------------------------------------------------------------
Version Information: Microsoft .NET Framework Version:2.0.50727.42; ASP.NET
Version:2.0.50727.42

Thank you.

"John K" wrote:

How do you hide the available functions (and syntax) that are normally
displayed when you browse to a webservice (e.g. httpx://xxx.com/CMgr.asmx)?

If you go to that page you will see a list of the available functions and
you can click on the function name to reveal the calling syntax. We need to
remove this documentation for security reasons. We do not want other people
to access the functions. We only want precompiled applications that know
what functions are available and the required calling syntax.

I tried a solution listed in an article at
http://www.15seconds.com/issue/040609.htm, but it did not work. It involved
adding a tag to the web.config file (<removename="Documentation"/> ).

Thank you.

[Kevin Yu [MSFT]]

Hi John,

There is some mistake on that page, it has to be <remove
name="Documentation" />

Kevin Yu
Microsoft Online Community Support

================================================== ==========================
==========================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ==========================
==========================

(This posting is provided "AS IS", with no warranties, and confers no
rights.)