Skip to content
This repository has been archived by the owner on Nov 8, 2024. It is now read-only.

Invalid code sample URLs when using multiple parameters & pct-encoding #36

Open
zdne opened this issue Feb 1, 2015 · 0 comments
Open

Comments

@zdne
Copy link
Contributor

zdne commented Feb 1, 2015

When there are multiple parameters in a Resource URI, and at least one with a pct-encoded character the rendered code sample show incorrect URL.

Consider following blueprint:

Request URL renders fine with:

# /notes{?foo%2Ebar}
### POST
+ Response 201 (application/json)

Appending one additional query parameter, let's say a results into incorrect URL in the example. Compare (correct):

screen shot 2015-02-01 at 9 30 09 pm

With incorrect:

screen shot 2015-02-01 at 9 29 54 pm

Also

The downstream effect here is that the incorrect URI is sent to the API server so the response is malformatted creating an error.

Originally reported at SO

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant