Re: Problem with WebServices WSDL auto gen feature
Alex DeJarnatt <[email protected]> Fri, 28 Jun 2002 10:17:30 -0700
| Newsgroups | gmane.comp.windows.devel.dotnet.general |
|---|---|
| Message-ID | <808430529A5A9A46AD69CC50D0C3AD3D02765DA1@red-msg-08.redmond.corp.microsoft.com> |
The "Documentation" protocol is used to service GET requests to foo.asmx (with or without a querystring). So this cuts off access to the auto-generated "help" page, and auto-generated WSDL, disco, and XSD. Users will see the message "Request format is unrecognized" if they try to get the help page or auto-generated description/discovery documents. alex -----Original Message----- From: Janis Braslins [mailto:[email protected]]=20 Sent: Friday, June 28, 2002 9:37 AM To: [email protected] Subject: [DOTNET] Problem with WebServices WSDL auto gen feature Greetings, In order to hide WSDL as well as Docs for our private web service, we've attemed add following modifications to our web service Web.Config file: <protocols> <remove name=3D"HttpGet"/> <remove name=3D"HttpPost"/> </protocols> The example above works fine, but as soon as we remove Documentation protocol, we get an error: <protocols> <remove name=3D"HttpGet"/> <remove name=3D"HttpPost"/> <remove name=3D"Documentation/"> </protocols> Results in: Source Error: 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.WebServiceHandlerFactory.CoreGetHandler (Type type, HttpContext context, HttpRequest request, HttpResponse response) +388 System.Web.Services.Protocols.WebServiceHandlerFactory.GetHandler (HttpContext context, String verb, String url, String filePath) +34 System.Web.HttpApplication.MapHttpHandler(HttpContext context, String requestType, String path, String pathTranslated, Boolean useAppConfig) +174 System.Web.MapHandlerExecutionStep.Execute() +78 System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +173 Any ideas why this is happening? From reading numerous post on deja.com as well as this boards, it seems like the solution should work and nobody seems to experience the same problem. Thank you for your help. You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com. You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.