Re^4: LWP::UserAgent : setting max_redirect to 0 yields 'Client-Warning: Redirect loop detected

... And so if one wants zero redirects, one should set max_redirect to 1 really ...

NO, that's wrong. Use only requests_redirectable method.

Comment on Re^4: LWP::UserAgent : setting max_redirect to 0 yields 'Client-Warning: Redirect loop detected Download Code

Replies are listed 'Best First'.
Re^5: LWP::UserAgent : setting max_redirect to 0 yields 'Client-Warning: Redirect loop detected by stevieb (Canon) on Mar 13, 2018 at 23:21 UTC
imho, `max_redirect => 0` should not warn. I'm with AnonyMonk above in that this smells like a bug (whether doc or code, I digress). If a parameter such as one that has "max" in its name is set to zero, it should not trigger a warning like this. Perhaps there's a good reason for it, but that would make it a doc bug. Otherwise, if I say "max something is zero", then any warnings/errors should be ignored, which would be a code bug. After a cursory review, the documentation does not handle this situation, and it should.	[reply] [d/l]

Replies are listed 'Best First'.

Re^5: LWP::UserAgent : setting max_redirect to 0 yields 'Client-Warning: Redirect loop detected
by stevieb (Canon) on Mar 13, 2018 at 23:21 UTC

imho, max_redirect => 0 should not warn. I'm with AnonyMonk above in that this smells like a bug (whether doc or code, I digress).

If a parameter such as one that has "max" in its name is set to zero, it should not trigger a warning like this.

Perhaps there's a good reason for it, but that would make it a doc bug. Otherwise, if I say "max something is zero", then any warnings/errors should be ignored, which would be a code bug.

After a cursory review, the documentation does not handle this situation, and it should.

[reply]
[d/l]