-
Notifications
You must be signed in to change notification settings - Fork 187
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
Use URL encoding when calling the API #5786
Comments
+
should be encoded in the API request to avoid the URL substitution
ResearchIn a first view, this problem could be caused in the API console of the plugin that could are coding the Search bar query:
API logs (using the search bar in Agents):
I tried in the API console of the plugin and seems here is the problem: API console request:
API logs:
|
ResearchThe path parameter of the Axios request is the value of the request: Example
path: The As workaround, if the request (path and query string) is typed using URL encoding, the character is received by the Wazuh server API as expected: The
API logs:
|
I will close the issue because the current behavior could be considered as expected. |
Description
The date values of the Wazuh API contain the
+
character. If the user does a query that contains this character, this should be encoded according to the framework co-workers. wazuh/wazuh#16899 (comment).This affects the new search bar #4312.
All our request must encode the URL as defined in the standard. The library we use to build requests should do this automatically for us. We must review if our usage prevents this behavior, or it is a bug.
The text was updated successfully, but these errors were encountered: