Reconsider PR #850: Wrong Fix for a Potentially Invalid Use Case #929

Activity

1. Kehrlann commented on Apr 22, 2026

   

   Kehrlann

   on Apr 22, 2026

   Contributor

   More actions

   Hey @jayaraman-venkatesan - thanks for the report!

   Rationale 1: I do understand that charset is not recognized, but it is encountered in the wild, and some servers do respect it.

   Rationale 2: yes, you are correct, tool names should be spec compliant. In fact, they are validated since #764 . But the content-type is also important for the "content" of the tool, including tool description or call arguments (see this test bit)

   If the server is too strict, you can work around it at the client transport level but overriding the value, e.g.:

   HttpClientStreamableHttpTransport.builder("...")
   	.httpRequestCustomizer((builder, method, endpoint, body, context) -> {
   		var built = builder.build();
   		var contentType = built.headers().firstValue("Content-Type").orElse("");
   		if (contentType.equalsIgnoreCase("application/json; charset=utf-8")){
   			builder.setHeader("Content-Type", "application/json");
   		}
   	})

   Unless there is very strong demand for this, we will not be addressing this issue.
2. Kehrlann

   closed this as completedon Apr 22, 2026
3. Kehrlann

   added

   wontfixThis will not be worked onThis will not be worked on

   area/client

   on Apr 22, 2026