You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm a little confused. Are you using attribute or convention-based routing? I see parts of both. I strongly recommend using one or the other. You may go cross-eyed otherwise. There are also some limitations in Web API's routing when both are used.
You're right, it came out a bit confusing. What i meant was that I tested both configurations, but I'm not using them both.
Either way, your suggestions didn't work. It may have something to do with my configuration, I don't know, but we've moved the language parameter to the Accept-Language HTTP header.
I think you made the right decision. The Accept-Language header will give you a lot more flexibility in requests because it supports multiple values with quality. You'll have the option to support language fallback without any changes to the API. :)
Uh oh!
There was an error while loading. Please reload this page.
Hello!
I just found out about this repo and was about to test it out on my current project but I can't seem to get thing to work as I want.
I had these routes defined, which I wanted to change so I could use URL path versioning.
I expected that changing the routes as follows it would still work:
After reading a bit on past issues I found out that it's not supposed to work. However, I haven't found a way to make this work.
My question is, can I make these routes work:
I have tried using this without success.
Thanks.
The text was updated successfully, but these errors were encountered: