-
Notifications
You must be signed in to change notification settings - Fork 683
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[#541] Play is no longer hardcoded to use utf-8 when communicating wi…
…th client. Http.Request now uses encoding specified in HTTP-Request or fallback to Play.defaultWebEncoding which default is utf-8. Http.Response can have different encoding for each response. It uses Play.defaultWebEncoding (default to utf-8) as default encoding for each response. You can modify the encoding for a specific request like this: Http.Response.current().encoding = "iso-8859-1" play.libs.WS is now fully encoding aware: default encoding for all WS-operations is now Play.defaultWebEncoding which default is set to utf-8. If developer want to use WS with other than default encoding, this can be done like this: WS.withEncoding("iso-8859-1").url(someUrl).get().getString() Play.defaultWebEncoding can be configured in application.conf with the property 'application.web_encoding'
- Loading branch information
Showing
107 changed files
with
800 additions
and
309 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Binary file not shown.
Binary file not shown.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.