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

Try it out option for unix get file content endpoint fails due to auto encoding / #60

Closed
jordanCain opened this issue Feb 28, 2019 · 1 comment
Labels
backlog bug Something isn't working

Comments

@jordanCain
Copy link
Contributor

Describe the bug
When selecting the try it out option for the unix get file content endpoint within the Swagger UI the request will fail for any provided path.

To Reproduce
Steps to reproduce the behavior:

  1. Go to Swagger UI
  2. Click on Unix files get content endpoint
  3. Enter a valid path to a file '/u/jcain/file.txt'
  4. Execute and see request auto encodes the path parameter slashes '/'

Expected behavior
The Swagger UI should not change the request path parameter

Additional context
There is a limitation with the Swagger UI see - swagger-api/swagger-ui#1637

@jordanCain jordanCain added bug Something isn't working backlog labels Feb 28, 2019
@std4lqi
Copy link

std4lqi commented Apr 20, 2019

The /api/v1/unixfiles/{path}/** in Swagger UI is a little misleading. I finally find it should be /api/v1/unixfiles/u/jcain/file.txt, without **.

One example would be helpful nearby the message of "Try it out function will not work ..."

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backlog bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants