Formatar conteúdo das requisições à API como UTF-8 #11
Conversation
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
O JSON da requisição é enviado ao servidor usando o encoding padrão ISO-8859-1 da classe StringEntity.
A RFC 8259 especifica que o encoding padrão do JSON é o UTF-8.
O resultado é que TTS com mensagens contendo caracteres especiais não são entregues como deveriam:
Nos endpoints legados apiX.totalvoice.com.br isso causa uma resposta 502 Bad Gateway do servidor.
No novo endpoint voice-api.zenvia.com as chamadas TTS são ditas com uma pausa na voz do bot onde deveria haver acentos.