Per request redirects #46
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…mechanism, with implementations for jul, log4j and slf4j
("Asymmetric use of Request.getUrl() & Request.getQueryParameters()")
Make sure we always properly construct the Request's url.
…sue/1 ("Update to Netty 3.2.2")
("Patch to allow hooking up a signature calculator (like OAuth)")
See the link above for more information. Patch Provided by Tatu Saloranta
…sue/3 ("InputStream.read(buffer) is assumed to always read all the data") See the link above for the complete description. Patch provided by Tatu Saloranta
…th Tatu Saloranta
Conflicts: src/main/java/com/ning/http/client/providers/NettyAsyncHttpProvider.java
…sue/4 ("Encode form param") See discussion on the link above
…sues/closed#issue/3 ("InputStream.read(buffer) is assumed to always read all the data") Support InputStream with bogus available return value
…r request from an AsyncHandler
…sue/14 ("Add an API an AsyncProvider can use to support zero copy of bytes.") And a new API that allow zero copy of bytes.
…sue/15 ("Make Response getter more robust, add helper") See issue description
…sue/16 ("NettyAsyncProvider optimization: avoid invoking onStatusReceived and onHeadersReceived multiple time per transaction") See issue for description.
0 - in request timeout is marker for not set value -1 - is infinite waiting
…unks. In that case we can't optimize
…sue/17 ("Do not set a default Content-Type") See issue description
…sue/10 ("Parameter encoding issue executing a request built with RequestBuilder") Patch provided by: Erwan Loisant
…sue/20 ("The current reaper may close connection event if they are active") See description.
Conflicts: src/main/java/com/ning/http/client/providers/NettyAsyncHttpProvider.java
Got it overwritten by last merge.
When location (or host + location in case of relative locations) is same as uri, return with redirect status code rather than looping until maxRedirects exception.
allow urls such as http://youtu.be/26dBZ7DPglE?a (pattern used by a lot of url shorteners)
…g redirection or not on a per request base, chaining
|
That's not right, it should be one commit. |
This pull request was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As discussed on the mailing list, here is a "setFollowRedirect()" method on the builder, to be included in the chain when building a request.