Open sixlettervariables opened 9 years ago
@sixlettervariables
Can it work to make path=/*
? See detail in:
http://www.asp.net/web-api/overview/odata-support-in-aspnet-web-api/odata-v4/odata-actions-and-functions
That does not work if you host multiple applications under /
.
For the path attribute I have path="*." Note the period after the asterisk.
That does not work with multiple WebApps under /
.
Can you try the unqualified function call? See detail at http://odata.github.io/WebApi/#06-01-custom-url-parsing:
This has been a particularly vexing issue when dealing with IIS, so I understand if your team has absolutely zero idea how to fix it. In a nutshell: how do you make IIS route OData without failing?
The OData WebApi configuration is the following (redacted as necessary):
With the following example controller:
When you query something like,
http://localhost/OData/Xyz/$count
, you get the number as expected. When you query something like,http://localhost/OData/Xyz/Default.Abc(yes=true)/$count
, you get an HTTP 500 error with an HRESULT of0x800703e9
(stack overflow).I've tried all manner of witchcraft and tomfoolery to get periods working in a URL (never thought folks would ever use those now did you IIS!), which doesn't appear to work for this either. The
Web.config
contains the usual incantations to allow IIS+OData to pretend to function:Due to similar errors, we've already given up on using
TimeSpan
in a URL (colons man...). Is there a way to make IIS and OData work? Or should we give up and use a self-hosted service?