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

fix: support non-json bodies #76

Merged
merged 3 commits into from
Jan 2, 2025
Merged

fix: support non-json bodies #76

merged 3 commits into from
Jan 2, 2025

Conversation

aeneasr
Copy link
Member

@aeneasr aeneasr commented Jan 2, 2025

Now supports forwarding non-json bodies.

Closes #72
Closes #68
Closes #70

Related Issue or Design Document

Checklist

  • I have read the contributing guidelines
    and signed the CLA.
  • I have referenced an issue containing the design document if my change
    introduces a new feature.
  • I have read the security policy.
  • I confirm that this pull request does not address a security
    vulnerability. If this pull request addresses a security vulnerability, I
    confirm that I got approval (please contact
    [email protected]) from the maintainers to push
    the changes.
  • I have added tests that prove my fix is effective or that my feature
    works.
  • I have added the necessary documentation within the code base (if
    appropriate).

Further comments

@aeneasr aeneasr changed the title fix: request body handling fix: support non-json bodies as well Jan 2, 2025
@aeneasr aeneasr changed the title fix: support non-json bodies as well fix: support non-json bodies Jan 2, 2025
@aeneasr aeneasr merged commit 240fba8 into main Jan 2, 2025
7 checks passed
@aeneasr aeneasr deleted the fix/empty-body branch January 2, 2025 10:58
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.

next-edge proxy dont work with new zstd encoding
2 participants