How to pass a datetime parameter?

by

The problem is twofold:

1. The . in the route

By default, IIS treats all URI’s with a dot in them as static resource, tries to return it and skip further processing (by Web API) altogether. This is configured in your Web.config in the section system.webServer.handlers: the default handler handles path="*.". You won’t find much documentation regarding the strange syntax in this path attribute (regex would have made more sense), but what this apparently means is “anything that doesn’t contain a dot” (and any character from point 2 below). Hence the ‘Extensionless’ in the name ExtensionlessUrlHandler-Integrated-4.0.

Multiple solutions are possible, in my opinion in the order of ‘correctness’:

  • Add a new handler specifically for the routes that must allow a dot. Be sure to add it before the default. To do this, make sure you remove the default handler first, and add it back after yours.
  • Change the path="*." attribute to path="*". It will then catch everything. Note that from then on, your web api will no longer interpret incoming calls with dots as static resources! If you are hosting static resources on your web api, this is therefor not advised!
  • Add the following to your Web.config to unconditionally handle all requests: under <system.webserver>: <modules runAllManagedModulesForAllRequests="true">

2. The : in the route

After you’ve changed the above, by default, you’d get the following error:

A potentially dangerous Request.Path value was detected from the client (:).

You can change the predefined disallowed/invalid characters in your Web.config. Under <system.web>, add the following: <httpRuntime requestPathInvalidCharacters="&lt;,&gt;,%,&amp;,*,\,?" />. I’ve removed the : from the standard list of invalid characters.

Easier/safer solutions

Although not an answer to your question, a safer and easier solution would be to change the request so that all this is not required. This can be done in two ways:

  1. Pass the date as a query string parameter, like ?date=2012-12-31T22:00:00.000Z.
  2. Strip the .000 from every request. You’d still need to allow :‘s (cfr point 2).

More Related Contents:

  1. Returning binary file from controller in ASP.NET Web API
  2. ASP.NET Web API – PUT & DELETE Verbs Not Allowed – IIS 8
  3. Accessing Session Using ASP.NET Web API
  4. Asp.NET Web API – 405 – HTTP verb used to access this page is not allowed – how to set handler mappings
  5. How to support HTTP OPTIONS verb in ASP.NET MVC/WebAPI application
  6. ASP.NET Web API OperationCanceledException when browser cancels the request
  7. Could not load file or assembly ‘System.Net.Http, Version=2.0.0.0 in MVC4 Web API
  8. Can You Determine Timezone from Request Variables?
  9. CORS support for PUT and DELETE with ASP.NET Web API
  10. Is there a way to force ASP.NET Web API to return plain text?
  11. WebAPI to Return XML
  12. ASP.NET Web API 2: How do I log in with external authentication services?
  13. Custom Authorization in Asp.net WebApi – what a mess?
  14. ASP.NET DateTime Picker
  15. Can I incorporate both SignalR and a RESTful API?
  16. How to Customize ASP.NET Web API AuthorizeAttribute for Unusual Requirements
  17. How to get POST data in WebAPI?
  18. Force CamelCase on ASP.NET WebAPI Per Controller
  19. How to return raw string with ApiController?
  20. ASP.net MVC4 WebApi route with file-name in it
  21. Web API Queryable – how to apply AutoMapper?
  22. Is there a default verb applied to a Web API ApiController method?
  23. ‘System.Net.Http.HttpContent’ does not contain a definition for ‘ReadAsAsync’ and no extension method
  24. User Authentication in ASP.NET Web API
  25. ASP.NET core JWT authentication always throwing 401 unauthorized
  26. All requests to ASP.NET Web API return 404 error
  27. Is it possible to access HttpContext.Current.Session from Web API
  28. Is there a way to handle form post data in a Web Api controller?
  29. URL encoded colon resolves in 400 Bad Request
  30. Is there a recommended way to return an image using ASP.NET Web API

Leave a Comment