We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hello, have a question regarding whitespace encoding in filters.
So normally whitespace can be encoded with either + or %20, such as
+
%20
name=first%20last or name=first+last
name=first%20last
name=first+last
I notice that when using django-rql, + is decoded as an actual + symbol, such that name=namewith+ and name=namewith%2B are the same
name=namewith+
name=namewith%2B
Is this intended? While we can enforce it to use %20, by default https://developer.mozilla.org/en-US/docs/Web/API/URLSearchParams encodes whitespace as + so this might be an issue to non suspecting clients consuming the API
django-rql version used: 4.4.0
4.4.0
The text was updated successfully, but these errors were encountered:
maxipavlovic
No branches or pull requests
Hello, have a question regarding whitespace encoding in filters.
So normally whitespace can be encoded with either
+
or%20
, such asname=first%20last
orname=first+last
I notice that when using django-rql,
+
is decoded as an actual + symbol, such thatname=namewith+
andname=namewith%2B
are the sameIs this intended? While we can enforce it to use %20, by default https://developer.mozilla.org/en-US/docs/Web/API/URLSearchParams encodes whitespace as
+
so this might be an issue to non suspecting clients consuming the APIdjango-rql version used:
4.4.0
The text was updated successfully, but these errors were encountered: