Skip to content

[writeHead] survive if http.serverResponse.writeHead() re-defined #166

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

Closed
wants to merge 1 commit into from

Conversation

mrose17
Copy link

@mrose17 mrose17 commented Jul 30, 2015

apparently one of the libraries used in my project redefines http.serverResponse's writeHead() ... you have to love those javascript frameworks. anyway, this "fix" will work regardless of whether or not writeHead() has been changed. thanks!

apparently one of the libraries used in a project redefines
@brettz9
Copy link
Collaborator

brettz9 commented Jul 24, 2021

As mentioned in #224, I guess we could protect overwrites to writeHead, but what's to prevent someone from rewriting setHeader? If it's a common enough use case to overwrite writeHead, I could add the preventative measure, esp. with a test. Thanks!

@brettz9
Copy link
Collaborator

brettz9 commented Jan 11, 2022

Closing as no response, but feel free to file a new PR/issue if you can clarify per #166

@brettz9 brettz9 closed this Jan 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants