For example, if your proxy returns a Set-Cookie header, and you attempt to add a new Set-Cookie header to the response, all the previous Set-Cookie headers will be lost. This functionality makes sense for headers that should only be specified once, but for multi-use headers like Set-Cookie the list should be appended instead of replaced. My particular use case for this was adding an upstream cookie after an auth_request.
If this is an intended feature as #18 suggests, maybe it should be added to the README.
For example, if your proxy returns a
Set-Cookieheader, and you attempt to add a newSet-Cookieheader to the response, all the previousSet-Cookieheaders will be lost. This functionality makes sense for headers that should only be specified once, but for multi-use headers likeSet-Cookiethe list should be appended instead of replaced. My particular use case for this was adding an upstream cookie after anauth_request.If this is an intended feature as #18 suggests, maybe it should be added to the
README.