Hi,
is it possible to have a route uppercase?
I tried both here, but doesn’t seem to work:
return [
//'resources' => [
// 'user' => ['url' => '/Users']
//]
'routes' => [
['name' => 'Users#index', 'url' => '/Users', 'verb' => 'GET']
]
];
It looks like routes should be case sensitive.
https://www.w3.org/TR/WD-html40-970708/htmlweb.html
And implementations of this api looks like they are using the case:
urlpatterns = [
# This endpoint is used soley for middleware url purposes.
re_path(r'^$',
views.SCIMView.as_view(implemented=False),
name='root'),
re_path(r'^\.search$',
views.SearchView.as_view(implemented=False),
name='search'),
re_path(r'^Users/\.search$',
views.UserSearchView.as_view(),
name='users-search'),
re_path(r'^Users(?:/(?P<uuid>[^/]+))?$',
views.UsersView.as_view(),
name='users'),
re_path(r'^Groups/\.search$',
views.GroupSearchView.as_view(),
name='groups-search'),
And the api I’m trying to implement describes routes with uppercase:
The System for Cross-domain Identity Management (SCIM) specification is an HTTP-based protocol that makes managing identities in multi-domain scenarios easier to support via a standardized service. Examples include, but are not limited to,...
Thanks for your help!
Ok, never mind, I was testing the wrong url…
So this is possible
And this actually works:
'resources' => [
'user' => ['url' => '/Users']
]
Please note that it might be error prone depending on proxies, webservers and other things involved in the chain.
We heavily recommend to only use lowercase URLs.
If you want to ignore that recommendation you should at least make sure the URL is only used in one way and not both urls: /users and /Users are being used for different things.