fix: correctly set `x-forwarded-*` in Middleware #57815
kodiakhq
merged
17 commits into
canary
from
fix/x-forwarded-headers-middleware
add test
187a8e09
cleanup stripping internal headers
75a4c49e
move injecting `x-forwarded-*` headers higher up
4d7cbe56
fix host
c5de9f85
fix lint
10831a95
fix lint
edb14bae
Merge branch 'canary' into fix/x-forwarded-headers-middleware
dc30aeb8
cleanup
94649b2b
use original request for all x-forwarded-* header values
9eaa2a1c
stop double setting x-forwarded-headers by proxy
c4a9b766
Merge branch 'fix/x-forwarded-headers-middleware' of https://github.c…
8552ef78
balazsorban44
commented
on 2023-11-01
add comment
dd8ccef4
use `this.hostname` and `this.port`
b1038c21
manually set `x-forwarded-host` header on `http-proxy`
72972bbc
revert `x-forarded-proto` changes in `resolve-routes.ts`
bfc8458e
allow reading `remoteAddress` from socket
52f70211
balazsorban44
commented
on 2023-11-01
huozhi
approved these changes
on 2023-11-01
![kodiakhq[bot]](https://avatars.githubusercontent.com/in/29196?v=4&s=60)
Merge branch 'canary' into fix/x-forwarded-headers-middleware
964c1859
Reviewers
Assignees
No one assigned
Labels
created-by: Next.js team
locked
Milestone
No milestone
Login to write a write a comment.
Login via GitHub