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

Clarify headers config option description #33484

Merged

Conversation

lobsterkatie
Copy link
Contributor

Reading over this page, it wasn't immediately clear to me if these were headers which would get read off of the incoming request, or headers to be added to the outgoing response.

Documentation / Examples

  • Make sure the linting passes by running yarn lint

@styfle styfle requested a review from molebox January 20, 2022 15:38
Reading over this page, it wasn't immediately clear to me if these were headers which would get read off of the incoming request, or headers to be added to the outgoing response.
@lobsterkatie lobsterkatie force-pushed the kmclb-clarify-headers-config-option-docs branch from 0dfc848 to d168e47 Compare January 24, 2022 23:55
@kodiakhq kodiakhq bot merged commit eba64c2 into vercel:canary Jan 25, 2022
@lobsterkatie lobsterkatie deleted the kmclb-clarify-headers-config-option-docs branch January 26, 2022 16:17
natew pushed a commit to natew/next.js that referenced this pull request Feb 16, 2022
Reading over this page, it wasn't immediately clear to me if these were headers which would get read off of the incoming request, or headers to be added to the outgoing response.



## Documentation / Examples

- [X] Make sure the linting passes by running `yarn lint`
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 26, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants