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
Some linters will discourage and warn on such "conflicts" but basically, we need to check static path first: https://domain.com/foo/bar/list
Then, based on type, (integer) or (string), you know which route to take.
I'm curious to know if wallarm will handle these without issue since request and response would be different in all 3 routes.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi,
Does anyone knows if Wallarm can handle Ambiguous paths ?
For example:
https://domain.com/foo/{integer}/list
https://domain.com/foo/{string}/list
https://domain.com/foo/bar/list
Some linters will discourage and warn on such "conflicts" but basically, we need to check static path first:
https://domain.com/foo/bar/list
Then, based on type, (integer) or (string), you know which route to take.
I'm curious to know if wallarm will handle these without issue since request and response would be different in all 3 routes.
Thanks in advance
Best Regards
Beta Was this translation helpful? Give feedback.
All reactions