Expected behavior
According to RFC 7578 section 8:
The multipart/form-data media type has no required parameters other than boundary and no optional parameters. However, jmeter adds a charset parameter to the Content-Type header when sending multipart/form-data requests.
The Content-Type header should only contain the boundary parameter:
Content-Type: multipart/form-data; boundary=6WHBdCwuCrCqKt-bDCQyRLPETfeXcy-5twdnz
Actual behavior
The Content-Type header includes an invalid charset parameter:
Content-Type: multipart/form-data; boundary=6WHBdCwuCrCqKt-bDCQyRLPETfeXcy-5twdnz; charset=UTF-8
Steps to reproduce the problem
- Create an HTTP-Request Sampler
- Set the method to POST
- Add a file
- Check the
Use multipart/form-data box
- Run the request and inspect the headers of that request
JMeter Version
5.6.3
Java Version
No response
OS Version
No response
Expected behavior
According to RFC 7578 section 8:
The
multipart/form-datamedia type has no required parameters other thanboundaryand no optional parameters. However, jmeter adds acharsetparameter to theContent-Typeheader when sendingmultipart/form-datarequests.The
Content-Typeheader should only contain theboundaryparameter:Content-Type: multipart/form-data; boundary=6WHBdCwuCrCqKt-bDCQyRLPETfeXcy-5twdnzActual behavior
The
Content-Typeheader includes an invalidcharsetparameter:Content-Type: multipart/form-data; boundary=6WHBdCwuCrCqKt-bDCQyRLPETfeXcy-5twdnz; charset=UTF-8Steps to reproduce the problem
Use multipart/form-databoxJMeter Version
5.6.3
Java Version
No response
OS Version
No response