-
Notifications
You must be signed in to change notification settings - Fork 92
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Emails in path are not allowed by default #98
Comments
That's true. By default, bidi only allows a limited extension of The reasoning is to prevent injection attacks. This is just the case where Malcolm Sparks Email: malcolm@juxt.pro JUXT LTD. On 22 November 2015 at 22:38, Imre Kószó notifications@github.com wrote:
|
Thanks for the explanation. I opened one for yada about the related path problem: juxt/yada#41 |
I came across a situation where I needed to create an api with a path like "/foo/by-email/aaa@example.com" where the email is a route param. It appears bidi does not let you do that currently without a regex specification of the email. Please see example below:
Not sure if this is intended or just an oversight.
Using a regex to specify format is fine, but I'm using it together with yada and it thinks the regex is a path element.
The text was updated successfully, but these errors were encountered: