Adjust node max-http-header-size setting #201
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When using the
push-to-registry
option some users have encountered header overflow issues when interacting with certain OCI registries.By default, node limits the total size of headers received in a single response to 16KB. We have seen certain interactions with the Google Artifact Registry API return headers totaling 21KB.
This change updates the maximum allowed header size to 32KB in order to give us some more breathing room when interacting with these registries.