Call an IIS Web Service without the .asmx extension?

Add a wildcard mapping, which will route all requests through ASP.NET.

Add a wildcard mapping, which will route all requests through ASP. NET: professionalaspnet.com/archive/2007/07/2... You'll also need to do some URL rewriting, to allow the incoming request localhost/soap/MyWebService to map to localhost/soap/MyWebService.asmx. weblogs.asp.net/scottgu/archive/2007/02/... Basically, you could add something like the following to your Application_BeginRequest method: string path = Request.

Path; if (path. Contains("/soap/") &&!path. EndsWith(".

Asmx")) Context. RewritePath(path + ". Asmx"); I haven't tested it (and it's a HACK) but it should get you started.

While this solution does work it only works on systems running IIS 6 or above. – jercra Mar 4 '09 at 6:47 It's possible to add a wildcard mapping to IIS 5. X, but the steps are different.

– Brannon Mar 4 '09 at 8:53 Yeah, you can add a wildcard mapping to IIS 5. X but there is a bug when it comes to web service in which you'll get an error about the verb not being allowed. The bug is pretty well noted on the ASP.Net message boards.

– jercra Mar 5 '09 at 17:19.

You could also put it in a directory by itself, then in IIS set it as a default document. On server: C:/mywebsite. Com/mywebservice/mywebservice.

Asmx In IIS set mywebservice. Asmx as a default document On the web: mywebsite.com/mywebservice.

Tried that and it didn't work. – jercra Mar 4 '09 at 4:03.

It seems to me that there's something very wrong with the PHP client. They should not be interepreting the URL for the service in any way. Whatever URL is specified in server metadata or client configuration is the URL they should use.

I don't know PHP, but can anyone tell me why it makes any sense for PHP to care how many dots there are in a URL? I can't see that it should matter to any client whether my service is at localhost/foo/bar or "http://localhost/foo/b.a.r. Asmx?

PHP=0".

The issue is not that PHP cares about how many dots there are. It's that the PHP client is not under my control and the address is hardcoded to localhost/foo/bar and IIS expects localhost/foo/bar.asmx. I needed IIS to understand that requests without .

Asmx should still be processed. – jercra Mar 5 '09 at 17:21 This begins to confirm my belief why in the world would it be a good idea for any client of a web service or other resource to hard-code the URL? URLs change.

They should take the URL from some configuration store. – John Saunders Mar 5 '09 at 22:32.

In php you have to call the wsdl only, you don't need the asxm or that kind of stupid things that . Net do. One simple example $wsdl = "http://domain/wsdlfile.

Wsdl"; //url to wsdl $client = new SoapClient($wsdl,array('trace' => 1,'encoding' => 'UTF-8','exceptions' => 0)); $Return = $client->callfunction(); echo htmlspecialchars($client->__getLastResponse()); that's all.

1 Pardon me, but not even PHP can call a WSDL. A WSDL simply describes the service that PHP will later call. The WSDL will usually contain the URL of the actual service, which will be the stupid .

Asmx file. – John Saunders Aug 16 '09 at 22:40.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.

Related Questions