-
Notifications
You must be signed in to change notification settings - Fork 50
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
Querying the API using http with escaped characters doesn't work properly #88
Comments
This issue has been automatically marked as stale because it has not been updated for at least 6 months. If you can still reproduce this issue on the current release or on Thank you for all your contributions! |
@carbonin is this still a valid issue? If yes, please remove the stale label. If not can you close. |
Yeah, still a valid issue. Just reproduced it.
|
This issue has been automatically marked as stale because it has not been updated for at least 6 months. If you can still reproduce this issue on the current release or on Thank you for all your contributions! |
@carbonin is this still an issue? |
Yup, still there:
|
It looks like the redirect from http to https is re-escaping any
%
characters in the URL string, even if they have been escaped previously.For example:
Entering
http://<host>/api/vms?expand=resources&filter[]=id=1
redirects tohttps://<host>/api/vms?expand=resources&filter%5b%5d=id=1
and prints the json response for the one vm as expected.Entering
http://<host>/api/vms?expand=resources&filter%5b%5d=id=1
(redirect url with the "s" removed) redirects tohttps://<host>/api/vms?expand=resources&filter%255b%255d=id=1
which is not a valid filter and which gives me the json for all of the vms.As 0x25 is the ascii hex for the % symbol, it looks like the symbols are getting re-escaped during the redirect. I'm thinking this has something to do with our rewrite rule here https://github.com/ManageIQ/manageiq-appliance/blob/master/COPY/etc/httpd/conf.d/manageiq-http.conf#L10-L13
/cc @abellotti
The text was updated successfully, but these errors were encountered: