Matthias Endler
Matthias Endler
Thanks. What's interesting is that this works as expected: ``` lychee https://talon.one ``` So it has to have something to do with https://docs.talon.one, which I'm assuming runs on totally different...
I am not aware of any wildcard issues. Can you check the `reqwest` issues? That's what we use under the hood.
That's strange. I checked the response headers and can only see these? ``` HTTP/2 200 accept-ranges: bytes content-disposition: inline; filename="index.html" content-type: text/html; charset=utf-8 date: Tue, 18 Nov 2025 11:11:46 GMT...
Hum, well, it could still be a bug in lychee, so let's keep it open for a bit. I would like to investigate more if I get the chance. Apologies...
While I don't think I can fix the immediate issue, I think we can at least provide a slightly better error message. Tried my luck in #1927. The reason why...
Yes, I also got the error, but your branch works indeed! ``` 🔍 59 Total (in 0s) ✅ 57 OK 🚫 0 Errors 👻 2 Excluded ``` If this also...
Good times. Thanks for the feedback and thanks to @thomas-zahner, who did all the work.
Sorry. 😅
In my opinion, the best behavior would be to display warnings for non-2xx status codes on CLI inputs. When a URL provided directly as a command-line argument returns a 4xx...