Skip to content
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

URI encoded marathon application ids are double encoded #80

Closed
lo1tuma opened this issue Feb 11, 2015 · 1 comment
Closed

URI encoded marathon application ids are double encoded #80

lo1tuma opened this issue Feb 11, 2015 · 1 comment

Comments

@lo1tuma
Copy link

lo1tuma commented Feb 11, 2015

The README about the REST API says that marathon application ids have to be URI encoded. The given examples in the documentation are actually double encoded. I’ve tried both, single encoded and double encoded marathon app ids, the REST API only works with double encoded ids.

  1. Example from documentdation: curl -i -X DELETE http://localhost:8000/api/services/%252Fapp-1
  2. Decoded: http://localhost:8000/api/services/%2Fapp-1
  3. Decoded again: http://localhost:8000/api/services//app-1
@j1n6
Copy link
Contributor

j1n6 commented Apr 18, 2015

closed by #109

@j1n6 j1n6 closed this as completed Apr 18, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants