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(proxy): handle responses with no content #433

Merged
merged 1 commit into from
Jul 10, 2023
Merged

fix(proxy): handle responses with no content #433

merged 1 commit into from
Jul 10, 2023

Conversation

vushe
Copy link
Contributor

@vushe vushe commented Jul 10, 2023 •
edited

🔗 Linked issue

unjs/nitro#1275

❓ Type of change

  • 📖 Documentation (updates to the documentation, readme, or JSdoc annotations)
  • 🐞 Bug fix (a non-breaking change that fixes an issue)
  • 👌 Enhancement (improving an existing functionality like performance)
  • ✨ New feature (a non-breaking change that adds functionality)
  • 🧹 Chore (updates to the build process or auxiliary tools and libraries)
  • ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

Prevent an error on responses without body like 204 No content

@pi0 pi0 changed the title fix(proxy): requests without body fix(proxy): handle responses with no content Jul 10, 2023
pi0
pi0 approved these changes Jul 10, 2023
View reviewed changes
Copy link
Member

@pi0 pi0 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@pi0 pi0 merged commit fb9e3e3 into unjs:main Jul 10, 2023
4 checks passed
@pi0 pi0 mentioned this pull request Aug 4, 2023
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@pi0 pi0 pi0 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.

None yet
2 participants
@vushe @pi0