mattcasters commented on issue #8507: URL: https://github.com/apache/hop/issues/8507#issuecomment-5809416926
This is the `charset` parameter on `Content-Type`, not a TLS fingerprint. Hop 2.19 sends Application type JSON as `application/json; charset=UTF-8` (`ContentType.APPLICATION_JSON` in HttpClient 5). Hop 2.17 sent `application/json` with no parameter. I posted the same dummy body to `https://app.omie.com.br/api/v1/geral/clientes/`: - `Content-Type: application/json` → HTTP 403 and Omie's normal JSON fault (invalid key). The request reached the API. - `Content-Type: application/json; charset=UTF-8` (also `utf-8` and `utf8`) → HTTP 500 and the SOAP Sender envelope in this ticket. - `text/xml; charset=UTF-8` does the same. `Accept`, `Accept-Encoding`, `User-Agent`, and HTTP/2 do not. The detailed "Request sent" block prints the entity content type before the headers. For Application type JSON that line is always `Content-Type: application/json; charset=UTF-8`, even when a Headers-tab value is what will go out. Workaround on 2.19: on the Headers tab set `Content-Type` to `application/json` with no charset. Leave Application type as JSON. The body stays UTF-8. Fix: https://github.com/apache/hop/pull/8569 — the mime type is sent alone unless the row sets `Content-Type` itself. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
