-
-
Notifications
You must be signed in to change notification settings - Fork 236
conditionally set headers (if not already set) in redirect response #190
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
conditionally set headers (if not already set) in redirect response #190
Conversation
hi @wesleytodd, could you help with getting these changes checked? I think you mentioned something along these lines as potentially acceptable. I'm being pushed by security officer to have this fixed and closed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
I am pretty sure I will be putting together a release for this in the coming days, so I will make sure this gets merged before then but I will leave it open so other contributors have a chance to see it again and provide any last minute feedback. |
fair enough, many thanks for coming back to me! :) |
@wesleytodd sorry for pushing, but is there any timeline on when the new release with this fix could be expected? |
…ect response (expressjs#190)" This reverts commit b51ab84.
…onse (expressjs#190) * conditionally set headers (if not already set) in redirect response * add new function description --------- Co-authored-by: ljeda <Lukasz.Jeda@pl.ibm.com>
suggested fix for possibility to override default headers in redirect response.
fixes #187