Vítor Vasconcellos

This also breaks the `{{upstreams}}` token in labels of containers using ingress networks. That is due to the container id being used to resolve which ingress networks the caddy container...

The `/proc/self/mountinfo` file won't work as a reliable solution to this problem. Some couple more tests, and I was able to completely remove all container id references from it: ```shell...

> Can you please give it a try? It would be nice to know that caddy-proxy is already usable with cgroup2. @lucaslorentz as far as I tested yesterday and today,...

> Thank you very much! I need to look at this more in detail. I was also thinking about using something completely different than ava for the tests. After I'm...

Rebased the PR on the current master. Most tests are failing, but thankfully no errors, just output differences, which is expected now that the project is using inheritance. The only...

> if you have good results with it then you can already make a pull request from your branch, best is to add a note about the `tsconfig` configuration to...

Here is an implementation for the rule targetting `Gio.Cancellable.connect`: ```json { "eslintConfig": { "env": { "node": false, "es2021": true, "browser": false, "commonjs": false, "shared-node-browser": false }, "rules": { "no-restricted-syntax": [...

No worries @JumpLink. I am in no hurry. Btw, thank you for the work you put into this project, and in keeping up with my stream of issues and PRs...

This issue completely slipped though my tests, thanks for finding it. I already came up with a solution that seems to be working fine, but this time I am going...

So, while I do agree that the bypass functionality need to be supported, I don't think just removing the check for the returned headers is the best approach. Does authelia...