Skip to content

Conversation

qxo
Copy link
Contributor

@qxo qxo commented Apr 20, 2019

change Whitelabel Error Page Content-Type to "text/html;charset=UTF-8"
or change AbstractErrorWebExceptionHandler.renderDefaultErrorView html content with <meta charset=\"utf-8\">

Otherwise " ⇢" maybe not work!

change Whitelabel Error Page  Content-Type  to "text/html;charset=UTF-8"
or change AbstractErrorWebExceptionHandler.renderDefaultErrorView html content with `<meta charset=\"utf-8\">`
@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged label Apr 20, 2019
@philwebb philwebb added the for: team-attention An issue we'd like other members of the team to review label May 14, 2019
@philwebb philwebb removed the for: team-attention An issue we'd like other members of the team to review label May 22, 2019
@bclozel bclozel changed the title Default html Content-Type should with UTF-8 Set UTF-8 as default charset for whitelabel HTML error pages May 27, 2019
@bclozel bclozel added type: enhancement A general enhancement and removed status: waiting-for-triage An issue we've not yet triaged labels May 27, 2019
@bclozel bclozel added this to the 2.2.0.M4 milestone May 27, 2019
@bclozel bclozel changed the title Set UTF-8 as default charset for whitelabel HTML error pages Set UTF-8 charset for whitelabel HTML error pages May 27, 2019
bclozel pushed a commit that referenced this pull request May 27, 2019
This commit changes the HTTP response Content-Type for whitelabel
error pages with Spring WebFlux.

See gh-16611
@bclozel bclozel closed this in d46de7a May 27, 2019
bclozel added a commit that referenced this pull request May 27, 2019
* fix-whitelabel-with-charset:
  Polish "Set UTF-8 charset for whitelabel HTML error pages"
  Set UTF-8 charset for whitelabel HTML error pages
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: enhancement A general enhancement
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants