-
Notifications
You must be signed in to change notification settings - Fork 870
Open
Description
Checks
- I understand project setup issues should be asked on StackOverflow or in GitHub Discussions.
- I updated to latest
http-proxy-middleware
.
Describe the bug (be clear and concise)
The "Cookie" header is not automatically added to the redirected address.
Step-by-step reproduction instructions
When I inspected the requests with Burp, the redirected address was not receiving the "Cookie" header. However, when I changed the user agent, the user agent was indeed changing.
Expected behavior (be clear and concise)
The addition of the "Cookie" header to the redirected address.
How is http-proxy-middleware used in your project?
pnpm i http-proxy-middleware
What http-proxy-middleware configuration are you using?
`const proxy=createProxyMiddleware({
target: 'https://www.example.com/',
changeOrigin: true,
agent,
autoRewrite: true ,
followRedirects: true,
selfHandleResponse: true,
headers:{
"Cookie":"test=123"
},
on: {
proxyReq: (proxyReq, req, res,options) => {
}
}
});
function customProxy(req,res,next){
req.headers["Cookie"]='test='+getKey();
proxy(req,res,next);
}
app.use('/proxy',customProxy );
//app.use('/proxy',proxy);`
`
What OS/version and node/version are you seeing the problem?
win 10
node v21.7.1
Additional context (optional)
No response
SriganeshNk
Metadata
Metadata
Assignees
Labels
No labels