-
Hello @amorey ,
I am currently facing an issue using [@edge-csrf/node-http](https://github.com/kubetail-org/edge-csrf/tree/main/packages/node-http) with [next-http-proxy-middleware](https://github.…
-
### Related Feature
Feature request: -
### Description
- `directLoad: true` does not work and fails with Error: `EISDIR: illegal operation on a directory, read`
### Steps to Reproduce
S…
-
### Issue Description
Requests that reach the final server contain the `Host` header from the original request. If the destination server checks the header `Host` (eg: ingress in k8s cluster with `…
-
### Plugin Name
airbrake
### 📜 Description
We aren't able to use v3 of `http-proxy-middleware` as it requires manual migration changes.
Renovate PR: https://github.com/backstage/community-plugin…
-
We have some middlewares before the proxy middleware to handle setting cookies (like authentication and others).
We set cookies like this in previous middlewares: `res.cookie('name', 'value')`.
Re…
-
### Describe the feature you'd love to see
Hi,
Integrating support for Hono within http-proxy-middleware will be an awesome feature., especially considering Hono's widespread popularity as a web f…
-
protection for API keys
-
Currently auth middleware enables Traefik to protect services without authentication accessed from Ingress.
oauth2-proxy is supposed to also works as a co-container - it will proxy all requests to so…
-
It would be great if granian could handle X-Forwarded headers for a smooth experience with reverse proxies without depending on a special setup or another dependency. Just declare your trusted proxies…
-
Can you consider implementing handling for the `X-Forwarded-User` header to allow for user identity to be passed?
### Use Case
Enables Traefik middleware configuration:
```yaml
middlewares:
r…