Skip to content

Conversation

bdehamer
Copy link
Collaborator

Closes: #606

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.

@Copilot Copilot AI review requested due to automatic review settings August 23, 2025 23:31
@bdehamer bdehamer requested a review from a team as a code owner August 23, 2025 23:31
Copy link

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR increases the Node.js HTTP header size limit from the default 16KB to 32KB to resolve header overflow issues when using the push-to-registry option with certain OCI registries, particularly Google Artifact Registry.

  • Adds NODE_OPTIONS environment variable with --max-http-header-size=32768 to the attest action step

Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.

@bdehamer bdehamer merged commit ff19f40 into main Aug 25, 2025
19 checks passed
@bdehamer bdehamer deleted the bdehamer/node-max-http-header-size branch August 25, 2025 20:52
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.

OCIError: Error uploading artifact to container registry with Google Artifact Registry
2 participants