Closed jonasengelmann closed 1 year ago
The commit 434dbdb7eaa08e6560d1b8bb5cb77ffb1d349556
in the PR #313 will fix your issue. TBH the Træfik interpreter is painful because it doesn't interpret the Go code like the compiler does. Here the issue was Yægi didn't like the nil
return as a function even if we don't try to call it.
About the index issue I already asked them if it was normal that the plugins catalog didn't index the new releases but the answer was without any explanations. Anyway I'll try to merge that PR, tag the new version and cross my finger they will index this new release.
@jonasengelmann the version v1.6.32
is now available.
@darkweak Thanks for looking into this so quickly and also pushing Traefik to reindex their plugin index and keeping up with their unreliable interpreter. I can now successfully load all version! However unfortunately I still get the error in version v1.6.32
. I noticed that I probably forget to post the most important log message, it only showed up in the Traefik debug log, and wasn't registered as an error, so that is why I missed it at first:
level=debug msg="'500 Internal Server Error' caused by: net/http: HTTP/1.x transport connection broken: http: ContentLength=11 with Body length 0"
I think this line is triggering the error, but I was not able to fix the issue as I am not so proficient in Go. Do you have any idea?
Fixed by #317
@jonasengelmann can you retry and tell me if that's okay for you too?
@darkweak I just did a test with version v1.6.34
but sadly I still get the error. I think it might have to do with the difference between rq
and req
here. I quickly checked and rq.Body
is still being consumed, but I do not understand where exactly. Do you have an idea?
New version available, it should fix everything 🤞
Just tested it and now everything works! Many many thanks!
Sorry to bring this up again, but I just run a test with the refactored version. However, I was not able to load version v1.6.30 nor v1.6.31 as Traefik plugin.
But with the already refactored version (v.1.6.29) I do get this error:
Here is my test setup:
And this was my request, which does work fine without caching:
curl -X POST -i http://localhost -H "Content-Type: application/json" -d '{"test": 1}'