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.

Sign up for GitHub

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

Jump to bottom

fix: do not override Content-Type header #6

Merged
merged 1 commit into from
Nov 15, 2023
Merged

fix: do not override Content-Type header #6

merged 1 commit into from
Nov 15, 2023

Conversation

iamjamesim
Copy link
Contributor

What kind of change does this PR introduce?

Closes #4

What is the current behavior?

FunctionInvokeOptions overrides the specified Content-Type header value to application/octet-stream when body is of type Data.

What is the new behavior?

Functions are invoked with the specified Content-Type header value.

Additional context

Fix verified by:

  1. Running the added test case.
  2. Invoking a function that handles multipart/form-data requests.

@grdsdev grdsdev merged commit 272715d into supabase-community:main Nov 15, 2023
@grdsdev grdsdev mentioned this pull request Nov 15, 2023
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@grdsdev grdsdev grdsdev approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Content-Type header should not be overridden
2 participants
@iamjamesim @grdsdev