-
Notifications
You must be signed in to change notification settings - Fork 164
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
[Sharing NG] user/group search term does not work with special chars #8615
Comments
Hm, that's the github.com/CiscoM31/godata.TokenMatcher choking on the the ?. I am not whether that is actually a bug in go data or the ? needs any special escaping in odata. Still looking ... |
Don't know if it helps, but it pretty much happens with any special char. Also blanks, e.g. |
Yeah, the parser only accepts word characters for search literals: That is probably too strict. But we'd need to check the ODATA spec to be sure. |
@JammingBen The behavior of godata is actually correct. You need to quote the search phrase in double quotes if it contains anything else than word characters. So |
Thanks, this works perfectly fine!
Hmm good point. While it's a valid concern, I'd be fine with leaving it unsolved for now since it's quite the edge case. Web actually has several tests including special characters, however none of them include |
Describe the bug
The server responds with a
400
error when requesting users/groups via thegraph/v1.0/users
(orgraph/v1.0/groups
) endpoint while using a search term that includes special characters.Steps to reproduce
test?
test
(https://host.docker.internal:9200/graph/v1.0/groups?%24search=test
) -> works fine, the result will be the newly created grouptest?
(https://host.docker.internal:9200/graph/v1.0/groups?%24search=test?
or encoded - no differencehttps://host.docker.internal:9200/graph/v1.0/groups?%24search=test%3F
) -> doesn't workExpected behavior
The server responds with the newly created group
test?
.Actual behavior
The server responds with a
400
error:Token '?' is invalid
.@rhafer am I missing something, or is this a valid issue?
The text was updated successfully, but these errors were encountered: