We have been able to see it work, if we put the charset *between* the
multipart/form-data and the boundary. i.e.
Content-Type: multipart/form-data; charset=utf-8;
boundary=some-nonsense-here
Which should reasonably work for everyone, including this busted app. I
know that it messes with
I'm not arguing that Akka is doing the wrong thing.
But, I'm pretty screwed right now because significant functionality of the
app for which I'm proxying is broken due to this and it's probably going to
be my problem to fix :) So, is there any way that I can hook into the
parsing and rendering
"The "charset" parameter is used with some media types to define the
character set (section 3.4) of the data. When no explicit charset parameter
is provided by the sender, media subtypes of the "text" type are defined to
have a default charset value of "ISO-8859-1" when received via HTTP. Data
in c
Hi guys,
I've written a reverse-proxy with Akka-HTTP and I'm hitting a problem while
trying to interact with an ASP.NET app. The only interesting thing I can
see is that without the proxy, the Content-Type is lacking a charset but
the proxy adds charset=UTF-8.
I can't find a way to replicate
