Remove alterações PR (#364)#435
Merged
Merged
Conversation
This file contains hidden or 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
2 participants
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.
As alterações implementadas via PR (#364), quebra a compilação do Horse na versão 10.1 do Delphi (#433) e é uma forma ineficiente de corrigir o problema de encoding relatado.
No Delphi 10.0 (Seattle), a unit Web.HTTPApp.pas por padrão codifica o corpo das requisições em ANSI, a menos que um charset seja especificado no cabeçalho Content-Type, como é mostrado no print retirado do PR.
Para resolver isso de forma eficaz e garantir a compatibilidade, a solução mais simples é adicionar charset=utf-8 ao cabeçalho Content-Type. Dessa forma, a própria unit Web.HTTPApp do Delphi reconhecerá e aplicará a codificação UTF-8 corretamente, sem a necessidade de modificações no framework.
Há também uma RFC que ampara o uso de charset no content-type, RFC 9110