Skip to content
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

Can I set my own custom header for each request? #1382

Open
blue-hope opened this issue Nov 28, 2022 · 0 comments
Open

Can I set my own custom header for each request? #1382

blue-hope opened this issue Nov 28, 2022 · 0 comments
Labels
priority: p3 Desirable enhancement or fix. May not be included in next release. type: question Request for information or clarification. Not an issue.

Comments

@blue-hope
Copy link
Contributor

blue-hope commented Nov 28, 2022

The question may be a bit silly because I do not have a deep understanding of gax-nodejs and aip.

According to the generated code, it seems that the header is fixed with x-goog-api-client internally and Metadata is created with the header via metadataBuilder. Is it impossible to add other headers?

@blue-hope blue-hope added priority: p3 Desirable enhancement or fix. May not be included in next release. type: question Request for information or clarification. Not an issue. labels Nov 28, 2022
orgads pushed a commit to orgads/gax-nodejs that referenced this issue Jan 3, 2023
…oogleapis#1382) (googleapis#1208)

* chore: Enable Size-Label bot in all googleapis NodeJs repositories

Auto-label T-shirt size indicator should be assigned on every new pull request in all googleapis NodeJs repositories

* Remove product

Remove product since it is by default true
Source-Link: googleapis/synthtool@f1562fa
Post-Processor: gcr.io/cloud-devrel-public-resources/owlbot-nodejs:latest@sha256:bb4d47d0e770abad62699a4664ce6b9ff1629d50c276a6c75860a6a1853dd19b
@alexander-fenster alexander-fenster removed their assignment May 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: p3 Desirable enhancement or fix. May not be included in next release. type: question Request for information or clarification. Not an issue.
Projects
None yet
Development

No branches or pull requests

2 participants