Skip to content

Respect Rawl URL Setting for Grizzly Provider in 1.7.x branch #439

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

Merged
merged 1 commit into from
Dec 13, 2013

Conversation

gerdriesselmann
Copy link
Contributor

A backport of my prior pull request #437 to 1.7.x

gerdriesselmann added a commit to gerdriesselmann/async-http-client that referenced this pull request Dec 13, 2013
Even with my prior pull request AsyncHttpClient#439 applied, the query string was still escaped twice, when using raw URL. This change fixes it. 

The function addQueryString() - that I commented out - seems to do nothing that has not already be done when building the URI in the Request. Except it does not care for the isUseRawUrl() setting. If there's a subtle difference I did not notice, isUseRawUrl() should be added inside the body of that function.

All of async-http-client tests still pass. com.ning.http.client.async.QueryParametersTest has no tests for raw URLs, though. But our tests now show the same behavior for both Netty and Grizzly.
rlubke added a commit that referenced this pull request Dec 13, 2013
Respect Rawl URL Setting for Grizzly Provider in 1.7.x branch
@rlubke rlubke merged commit 3609d19 into AsyncHttpClient:ahc-1.7.x Dec 13, 2013
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

Successfully merging this pull request may close these issues.

3 participants