Make redirect history available

[RossLote]

I've been getting some strange redirect behaviour and I'd like a way to find out whet is happening. For the URL I'm fetching I've been getting a TooManyRedirects, message: Some("reached max redirects (5)") error.

I fetched the same URL using the python requests library and I only got 1 redirect so I think there may be a problem. I'm actually in charge of the entire stack and can assure you that there is only 1 redirect in the entire request cycle.

I've managed to get around it by setting the redirect limit to 6 but because I have no visibility of the history I can't find out what is going on.

Is there a reason the history is private?

[RossLote]

Did anyone see this?

[algesten]

I don't really have an answer to why the history is private more than the smaller the API the less headache to maintain ureq.

[algesten]

I welcome help on this for ureq 3.x.

• A new config option that is false by default.
• Collect each redirect location into a Vec
• Make Vec available through ResponseExt trait.