I've run into an interesting problem that I never encountered with XP or IIS 6.
Basically, I can't get a native Delphi (WebBroker) Web service server to work with a native Web service client in Windows 7 64-bit.
Here's the most basic breakdown. If I create a new Web service application in Delphi 2010 (or any version, back to Delphi 7), and access it using IE 8, I can see the HTML that the WSDLHTMLPublish component creates, but I can never get to the SOAP. In the same way, the WSDL Importer cannot get to the SOAP either. (I have IIS 7 configured to use a 32-bit application pool, and I have created a working Script Map to the Handler Mappings. In short, the 32-bit ISAPI Web service is running).
For example, I have a simple Web service server named TestService (created using the default sample interface generated when you create a new Web service server).
I installed it in a virtual directory named scripts.
If I enter the URL to the service in the address bar, IIS 7 displays the appropriate page.
If I put my mouse over the WSDL link for the ITestService, I see pathinfo part in the status bar. However, when I click this link, the address bar shows the full URL with pathinfo, but I see only the HTML from service (URL without pathinfo). There seems no way to get to the SOAP definition. IIS 7 seems to be ignoring everything after the script name (it is ignoring the pathinfo).
Additional evidence that IIS7 is stripping off the pathinfo is that if I pause my mouse over the ITestService link, the statusbar shows the service URL with a query string (no pathinfo). Clicking that link takes me to another HTML page, the one associated with the service and query string. However, any link that includes a pathinfo following the script name, takes me simply to the base URL (no pathinfo).
I have tested this in Delphi 7, Delphi 2010, and Delphi XE, with the same results (all on Windows 7 Ultimate 64-bit.
I am guessing that IIS7 is stripping off the pathinfo, since even the WSDL Importer cannot get to the SOAP definition. I get the same results with Chrome. In other words, it does not appear to be a browser issue.
Is this an IIS7 configuration issue?