Re: LWP::UserAgent Client-Warning 500 against HTTP standards? (Predates current standards)

WWW::Mechanize uses autocheck ;) its a nice default with a browser like that

https://github.com/libwww-perl/libwww-perl/issues/258 Pseudo-500 Errors Make Debugging Harder Than It Should Be #258

the rfc does not specify how libraries/apis ought to be implemented. Issue 258 argues the code should be 4xx but those are all server responses too

20+ years ago i learned LWP and about internal error on the first day

500 is the most famous error

Comment on Re: LWP::UserAgent Client-Warning 500 against HTTP standards? (Predates current standards)

Replies are listed 'Best First'.
Re^2: LWP::UserAgent Client-Warning 500 against HTTP standards? (Predates current standards) by Your Mother (Archbishop) on Sep 30, 2022 at 11:15 UTC
`autocheck` being on by default was a heinous and breaking change to WWW::Mechanize. It is the equivalent of a browser crashing every time there is a response that doesn’t match `->is_success`.	[reply] [d/l] [select]
Re^3: LWP::UserAgent Client-Warning 500 against HTTP standards? (Predates current standards) by Anonymous Monk on Sep 30, 2022 at 12:54 UTC
Seatbelts save lives	[reply]