-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Panic if abort directive is used #44
Comments
Hello @AlyoshaVasilieva thanks for this report, I'll try to fix that. Thank you for the minimal reproductible example. |
It seems the next minor version I'm working on patch that behavior and prevent the panic (darkweak/souin@master...feat/chore/refactoring-to-middleware-philosophy) and I plan to release that on the next week. Can you wait for that? |
Yes, no issues waiting. |
Hello @AlyoshaVasilieva, you can test the new version using |
I can't build it.
without spaces after
|
@AlyoshaVasilieva I think it's because you have spaces between |
Oh my bad, I'll push a new commit without the bump. The |
Can you try with this commit instead?
The dependency |
|
I'm trying to reproduce your issue on another laptop. |
I think
I'll try to release that asap to avoid these build constaints. |
Correct - but more specifically, |
The release is currently running 🤞 |
It's now available using |
It no longer panics! However, when trying to use redis requests hang forever.
I've set all those timeouts in an attempt to make it timeout and issue an HTTP error, but it doesn't:
I'm not actually sure I've set it up correctly, but I'm not getting any error messages. After attempting to enable logging*, this is all I see in the logs:
* caddyfile:
Well, it's a different issue now, the original one seems solved. This is a huge improvement over panicking, so thank you! |
I'll have a look at that and try to fix this weird behavior. I will add some e2e test cases to ensure redis works well. |
I found the error, it comes from the |
@AlyoshaVasilieva Can you try with |
It appears to be working, I can't find any further issue. Thanks! |
Thanks for your patience and your time for testing that! |
/etc/caddy/Caddyfile
:Start caddy, then do
curl http://127.0.0.1
. Result: Caddy dies.Built about 15 minutes ago with
xcaddy build --with github.com/caddyserver/cache-handler
This is a minimal repro. I have a service that only approved IPs are able to access, otherwise Caddy
abort
s the request, and when I hit it from an unapproved IP after adding caching it killed Caddy.The text was updated successfully, but these errors were encountered: