I'm setting up my first Ember.js / ASP.NET Web API combo. I'm at the point where the Ember client and the ASP.NET API are talking to eachother. If I enter the following URL into Chrome, it works.
), and configure itself based on the path properties/1
and the JSON in the HTTP response from the API.
Here's the rub, if I exclude the hash from the URL, IlS and the ASP.NET Web API take a crack at routing properties/1
(w/o the api
prefix) and strike out.
I need to configure IIS Express / ASP.NET Web API to work without the hash
. In other words, unless it sees /api
in the path (ex. /api/properties/1
), its job is to ignore the path.
Question 1: What is best name for this functionality? "History API"? "Fragment"? "Fragment Identifier"? Something else?
Question 2: I suspect I take care of this with a little bit of default routing in the ASP.NET Web API. Once I get a better handle on the name for this functionality, I'll be able to research the fix in ASP.NET Web API (or possibly IIS Express).