-
Notifications
You must be signed in to change notification settings - Fork 58
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
fix(plugins): traefik configuration parsing #305
fix(plugins): traefik configuration parsing #305
Conversation
Although now POST requests can be cached, I noticed that sending a POST request with a body leads to an error 500 using a whoami test setup. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM after the little fix.
Does the |
I am not so sure, I think it comes from Souin although there is no error message in the logs. This is my test setup:
Returns:
In the traefik logs I can only find this: However, sending the same curl request to whoami without Souin as middleware returns this: Content-Length: 403
Content-Type: text/plain; charset=utf-8
Date: Fri, 10 Feb 2023 20:44:29 GMT
Hostname: 36772703e6b3
IP: 127.0.0.1
IP: 172.18.0.2
RemoteAddr: 172.18.0.3:38002
POST / HTTP/1.1
Host: localhost
User-Agent: curl/7.85.0
Content-Length: 11
Accept: */*
Accept-Encoding: gzip
Content-Type: application/json
X-Forwarded-For: 172.18.0.1
X-Forwarded-Host: localhost
X-Forwarded-Port: 80
X-Forwarded-Proto: http
X-Forwarded-Server: f83398e7cec5
X-Real-Ip: 172.18.0.1
{"test": 1}⏎ Any idea? |
I dunno why that behavior happens. I'll have a look at that once I finish my work on the middleware refactoring (FYI master...feat/chore/refactoring-to-middleware-philosophy). |
Thank you for your contribution @jonasengelmann 🚀 |
Closes #304