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
[V2] Make sure the name field only contains the unreserved characters in RFC3986 #343
Comments
This tag might help:
|
@weichou1229 thanks for the information. Unfortunately, ulr_encoded tag is used to validate if a string is url-encoded or not, which is a little bit different to what we would like to validate. I'll implement a custom tag to validate that name field only allows RFC3986 section 2.3 defined unreserved characters, which should be |
…acters A custom validation tag to ensure name filed only allows RFC3986 unreserved characters fix edgexfoundry#343 Signed-off-by: Jude Hung <jude@iotechsys.com>
…acters Implement a new custom validation tag "edgex-dto-rfc3986-unreserved-chars" to ensure name fields only allows RFC3986 unreserved characters. fix edgexfoundry#343 Signed-off-by: Jude Hung <jude@iotechsys.com>
…acters Implement a new custom validation tag "edgex-dto-rfc3986-unreserved-chars" to ensure name fields only allows RFC3986 unreserved characters. fix edgexfoundry#343 Signed-off-by: Jude Hung <jude@iotechsys.com>
…acters Implement a new custom validation tag "edgex-dto-rfc3986-unreserved-chars" to ensure name fields only allows RFC3986 unreserved characters. fix edgexfoundry#343 Signed-off-by: Jude Hung <jude@iotechsys.com>
…acters Implement a new custom validation tag "edgex-dto-rfc3986-unreserved-chars" to ensure name fields only allows RFC3986 unreserved characters. fix edgexfoundry#343 Signed-off-by: Jude Hung <jude@iotechsys.com>
…acters Implement a new custom validation tag "edgex-dto-rfc3986-unreserved-chars" to ensure name fields only allows RFC3986 unreserved characters. fix edgexfoundry#343 Signed-off-by: Jude Hung <jude@iotechsys.com>
In 15-OCT-2020 Core WG meeting, we decided to use only unreserved characters in the name field according to RFC3986.
https://en.wikipedia.org/wiki/Percent-encoding
The text was updated successfully, but these errors were encountered: