Skip to content
This repository has been archived by the owner on Jan 1, 2019. It is now read-only.

Follow 301 redirects #43

Closed
brunoribeiro opened this issue Sep 29, 2016 · 4 comments
Closed

Follow 301 redirects #43

brunoribeiro opened this issue Sep 29, 2016 · 4 comments

Comments

@brunoribeiro
Copy link

brunoribeiro commented Sep 29, 2016

Are follow redirects disabled by default? Is there any config switch to enable redirects?

I know that in ning async-http-client I can use the RequestBuilder .setFollowRedirects(boolean), but could not find anything similar in parallec.

@jeffpeiyt
Copy link
Contributor

jeffpeiyt commented Sep 30, 2016

@brunoribeiro

Parallec supports supplying your own customized AsyncHttpClient object: http://www.parallec.io/docs/submit-task/#apis-on-http where you can set any config with it.

However, seems AsyncHttpClient/async-http-client#788 mentioned the older version of AHC has bugs in this config even if it set as true. For our internal usages (mostly for APIs) normally they are not redirected .

With parallec you can also build multi step work flows to handle redirected pages or simply provide the final url, such as in this example: http://stackoverflow.com/questions/39081350/parallel-ssh-with-executorservice/39671381#39671381

It is always possible to run the next step based on the analysis on previous step results.

@brunoribeiro
Copy link
Author

Understood, I am going to configure an AsyncHttpClient to follows redirects, and test my use cases.

@jeffpeiyt
Copy link
Contributor

@brunoribeiro BTW, #37 has details of the parallec with AHC upgraded to the latest version 2.0.15 (requires JDK8) it has not been tested in production but passed all the comprehensive tests.

@brunoribeiro
Copy link
Author

@jeffpeiyt great, I will test it as soon as I can.

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

2 participants