I'm having a problem getting ServiceStack to work with HTTPS in IIS6 and I can't seem to find any documentation on setting this up. Currently I have an endpoint setup like so - http://example.com/api.ashx. When I browse to this, i get the useful ServiceStack generated page which explains the APIs available at http://example.com/api.ashx/metadata. When i browse to https://example.com/api.ashx (notice https) i instead get this error message -
Server Error in '/' Application. The resource cannot be found. Description: HTTP 404. The resource you are looking for (or one of its dependencies) could have been removed, had its name changed, or is temporarily unavailable. Please review the following URL and make sure that it is spelled correctly. Requested URL: /api.ashx
I have the following set up in my web.config (as per example here - http://www.servicestack.net/ServiceStack.Hello/) -
<!-- ServiceStack: Required to host at: /api.ashx -->
<location path="api.ashx">
<system.web>
<httpHandlers>
<add path="*" type="ServiceStack.WebHost.Endpoints.ServiceStackHttpHandlerFactory, ServiceStack" verb="*"/>
</httpHandlers>
</system.web>
On my local Windows 7 box i'm running IIS7 and it works just fine but the test and live environments are still using IIS6 and i can't get it to work there.
Other regular aspx pages are working fine when using https.
I'd appreciate anyone who can give me a push in the right direction!
The problem with IIS 6 is that the IIS 6.0 request pipeline doesn't recognize a path without an ASP.NET extension e.g .aspx doesn't get passed to the ASP.NET isapi hander. So there are generally 2 options for getting this to happen so you can get ServiceStack to run on IIS 6:
Change the servicestack path in Web.Config from '*' to 'servicestack.ashx'
<system.web>
<httpHandlers> <add path="servicestack.ashx" type="ServiceStack.WebHost.Endpoints.ServiceStackHttpHandlerFactory, ServiceStack" verb="*"/> </httpHandlers>
</system.web>
Add a wildcard mapping for your virtual directory to pass all unhandled requests to ASP.NET: Follow these steps to create a wildcard script map with IIS 6.0:
mythz answer didn't work for me.
I got it working by adding a location tag to web.config with the servicestack configuration. I found that servicestack worked with path="*" - but took to many requests(Episerver) but solved it like this:
And then prefixed all Routes with the UniqueTag:
But note that option 2 from mythz's answer might also be required, because it was default setup in our solution.