302 Found redirects are not followed

[katrinafyi]

302 Found redirects are treated as a final status code rather than a redirect to be followed.

$ echo 'http://dx.doi.org/10.1007/978-3-540-74061-2_11'  | cargo  run - -v      
     [302] http://dx.doi.org/10.1007/978-3-540-74061-2_11 | Rejected status code (this depends on your "accept" configuration): Found

If you follow the suggestion and add 302 to the accept set, this just terminates the link check at the 302.

[mre]

I wonder if that's an issue with lychee or reqwest.

We have this redirect policy.

lychee/lychee-lib/src/client.rs

Line 434 in 8d51c60

fn redirect_policy(redirect_history: RedirectHistory, max_redirects: usize) -> redirect::Policy {

Not sure if there's anything more to that. Didn't dig much deeper.

[katrinafyi]

Yeah I couldn't figure out what causes this. It looks like reqwest and tower should correctly handle Found.

• https://docs.rs/tower-http/latest/src/tower_http/follow_redirect/mod.rs.html#273
• https://github.com/seanmonstar/reqwest/blob/ef5b239cbaa5e93607415bcf943c8f571da13e42/src/redirect.rs#L405