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
If I create a collection with a "+" in the name I can no longer interact with it. In Api call which use the collection name in the URL part.
It looks as if there is no escaping happening when building URLs for the typesense API
Does the user of this library need to escape the collection name before using the api and make assumption about the underlaying workings of the api?
String is used as is and server receives "foo bar"
Typesense-js Version: 1.7.2
Reported via bfritscher/typesense-dashboard#44
The text was updated successfully, but these errors were encountered:
Same with # which opens up malicious actors to deleting unauthorised rows when combined with badly designed IDs/validation.
#
In fact, one could delete an entire collection just by starting the document ID with a hash.
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
Description
If I create a collection with a "+" in the name I can no longer interact with it. In Api call which use the collection name in the URL part.
It looks as if there is no escaping happening when building URLs for the typesense API
Does the user of this library need to escape the collection name before using the api and make assumption about the underlaying workings of the api?
Steps to reproduce
Expected Behavior
Actual Behavior
String is used as is and server receives "foo bar"
Metadata
Typesense-js Version: 1.7.2
Reported via bfritscher/typesense-dashboard#44
The text was updated successfully, but these errors were encountered: