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

Golang functions: Multi value headers not working in local development #4575

Closed
kasperstorgaard opened this issue May 2, 2022 · 0 comments · Fixed by #4618
Closed

Golang functions: Multi value headers not working in local development #4575

kasperstorgaard opened this issue May 2, 2022 · 0 comments · Fixed by #4618
Assignees
Labels
area: functions type: bug code to address defects in shipped code

Comments

@kasperstorgaard
Copy link

Describe the bug

When running netlify dev with golang functions, multi value headers are not working, but works in deploy preview, prod etc.

(This is specifically hindering me from testing a gin-gonic adapter setup locally, as the adapter uses multi value headers extensively)

Steps to reproduce

  1. Run git clone git@github.com:kasperstorgaard/netlify-golang-fn-tester.git
  2. Navigate to cloned repository
  3. Run npx netlify dev OR npm i && node_modules/.bin/netlify dev
  4. Open localhost:8888/.netlify/functions/tester
  5. Inspect request response in tool of choice

Expected headers:

"x-single": "A"
"x-multi":  "B, C"

Actual headers:

"x-single": "A"

Configuration

[functions]
directory = "src"

Environment

System:
OS: macOS 11.6
CPU: (8) x64 Intel(R) Core(TM) i5-1038NG7 CPU @ 2.00GHz
Memory: 74.09 MB / 16.00 GB
Shell: 5.8 - /bin/zsh
Binaries:
Node: 16.14.2 - ~/.nvm/versions/node/v16.14.2/bin/node
npm: 8.5.0 - ~/.nvm/versions/node/v16.14.2/bin/npm
npmPackages:
netlify-cli: ^10.0.0 => 10.1.0
npmGlobalPackages:
netlify-cli: 10.0.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: functions type: bug code to address defects in shipped code
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants