-
Notifications
You must be signed in to change notification settings - Fork 9.1k
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
Disallow ? , space and # in paths #330
Comments
It looks like #69 rejected the idea of explicit support for matrix params in the spec, but the fact that they exist seem to argue that |
It's true, @earth2marsh - at least for now we decided not to support matrix params (it was part of the discussion in 2.0). Also, as explained here, I'm not entirely sure we should restrict it at all in the schema. I'm still glad the issue exists here, as it'll force me to consider it :) |
Because the URL and path are well specified in the standard, it's safe to restrict them. Disallowing |
Mime types are also well defined (in format). I get what issue you're trying to avoid here, which is more 'sever' than the problems that can occur in mime types, so it can be a good idea in this case. |
@mohsen1 Based on this discussion and the current OpenAPI Spec v3, do you believe there is more work needed to address this issue ? |
The syntax for path templates in the Paths Object is derived from the RFC, which already forbids As noted above, we do not plan to forbid |
Per URL specs
and
?
,#
should not be part of the path.I'm not sure about
=
.The text was updated successfully, but these errors were encountered: