Set URI encoding for embedded containers to UTF-8

[sbuettner]

Please set the default encoding for the embedded containers to UTF-8. Otherwise there are issues with extracting characters like german umlauts from the uri for example when using the @RequestParam annotation. Currently i have to register my own connector customizer:

new TomcatConnectorCustomizer() {
  @Override
  public void customize(Connector connector) {
    connector.setURIEncoding("UTF-8");
  }
}

[sbuettner]

👍

[LeRiton]

I don' want to open another issue for this same case, since this one has been closed ans @snicoll proposal at #542 was supposed to fix this issue.

I'm experiencing the exact same issue using SB 1.0.2.RELEASE with a simple dummy project.

Project has spring-boot-starter-web and spring-boot-starter-thymeleaf dependencies and use spring-boot-maven-plugin for run, defaulting to Tomcat.

Messages submitted through basic form

<form action="/" method="POST">
    <p>New message: <input type="text" name="text" /></p>
    <p><input type="submit" value="Submit" /> </p>
</form>

are facing this encoding issue, despite Tomcat's default encoding UTF-8 provided in this thread. Thymeleaf's template and HTML page encoding are UTF-8 too.

This could be fixed by adding

    @Bean
    public Filter characterEncodingFilter() {
        CharacterEncodingFilter characterEncodingFilter = new CharacterEncodingFilter();
        characterEncodingFilter.setEncoding("UTF-8");
        characterEncodingFilter.setForceEncoding(true);
        return characterEncodingFilter;
    }

to application, witch makes me think that server encoding still doesn't match default. Using server.tomcat.uri-encoding doesn't fix encoding.

Am I missing something?

[snicoll]

What this commit does is changing the way Tomcat parse URIs. If you have a form with a body, it's a different matter and you should specify it in your request.

There are a couple of issues that are somewhat related to this. A request to change the default in Spring from ISO-8859-1 to UTF-8 (SPR-11779) and a bug that could occur if you set the body encoding as it is now used as the URI encoding by Spring (SPR-11474)

Both are currently scheduled for the next release but if you don't want to set the body encoding or if you want to enforce UTF-8, your current filter is the recommended approach.

[LeRiton]

Thanks for the clarification!

[snicoll]

@LeRiton we further discussed this matter and there's a specific issue in boot now (see #1182)

[Farzan6118]

append the following property in application.properties:

spring.datasource.connection-properties=useUnicode=true;characterEncoding=utf-8;

hope it helps