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

HTTPCLIENT-2159: Invalid handling of charset content type parameter #483

Merged
merged 1 commit into from
Sep 29, 2024
Merged

HTTPCLIENT-2159: Invalid handling of charset content type parameter #483

merged 1 commit into from
Sep 29, 2024

Commits on Sep 29, 2024

  1. HTTPCLIENT-2159: Fix handling of charset in ContentType for specific … 

    …media types

 * Updated ContentType to ensure that no charset is included for media types like application/octet-stream, multipart/form-data, and image/*, which do not require a charset as per the RFC.
 * Refactored the toString() method to properly handle the omission of charset for these media types.
 * Adjusted the creation methods to better handle implicit charsets and added validation for reserved characters in MIME types.
    @arturobernalg
    arturobernalg committed Sep 29, 2024
    Configuration menu
    Copy the full SHA
    185778f View commit details
    Browse the repository at this point in the history