| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
When reporting header content errors specify header name in the message for easier debugging in user applications. Fix: nodejs#14754
|
How about more simply: 'The header content contains invalid characters: ' + name ? |
Sorry, something went wrong.
|
@mscdex I don't mind. Although, both are consistent with existing error messages. |
Sorry, something went wrong.
| debug('Header "%s" contains invalid characters', key); | ||
| throw new TypeError('The header content contains invalid characters'); | ||
| throw new TypeError( | ||
| 'The header content contains invalid characters ["' + key + '"]'); |
There was a problem hiding this comment.
If the error messages are being changed, it would be nice to migrate the files to use internal/errors at the same time.
Sorry, something went wrong.
There was a problem hiding this comment.
Specific change LGTM with a suggestion
Sorry, something went wrong.
|
The errors in lib/_http_outgoing.js is being migrated to use internal/errors(#14735). I've added the header name in the error message. |
Sorry, something went wrong.
|
@indutny ... can you give this a rebase? |
Sorry, something went wrong.
Sorry, something went wrong.
|
It appears your're right :-) |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
When reporting header content errors specify header name in the message
for easier debugging in user applications.
Fix: #14754
Checklist
Affected core subsystem(s)
http