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
No, this wasn't a colon issue. It was actually a bonehead mistake by me using the wrong routes. I used "/api/article" in some places, where it's supposed to be "/api/articles". I also noticed that I used the wrong route for "unfavorite" while going through and double checking. Oops.
When using a particular frontend (https://github.com/khaledosman/angular-realworld-example-app), it seems to have trouble with colons in the URL.
Examples:
GET of "https://localhost:7272/api/articles/my-article-title::c2SkJ9HO6UDK " returns with 405 method not allowed
GET of "https://localhost:7272/api/article/my-article-title%3A%3Ac2SkJ9HO6UDK" (which is what Swagger UI generates) works fine.
Is it possible that this is a server-side routing issue? How can that be fixed?
If not, may need to change the delimiter/structure of slugs.
The text was updated successfully, but these errors were encountered: