net-http 0.7.0+ requires to explicitly setting content type #79
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
net-http v0.7.0 (released Oct 2025) removed the automatic
Content-Type: application/x-www-form-urlencodedheader for POST requests. Without this header, GMO servers can't parse form parameters, resulting in errors likeE01190001 "Site ID not specified".問題: net-http v0.7.0（2025年10月リリース）で、POSTリクエストの
Content-Type: application/x-www-form-urlencodedヘッダーの自動付与が廃止されました。このヘッダーがないと、GMOサーバーがフォムパラメータを解析できず、E01190001「SiteIDが指定されていません」などのエラーが発生します。net-http Content-Type Change
Version: v0.7.0
Released: October 31, 2025
PR: ruby/net-http#207 - "Don't set content type by default"