I was able to verify that this is breaking the app in question, but not 
with Akka.  I merely added the charset to the request that was working, and 
it broke.

But I think I have a more fundamental problem: I can't see the raw request 
that came in from the client.  It, of course, is only represented using the 
Akka HTTP model and that model requires a charset for NonBinary 
ContentTypes.  So, if I wanted to try and force the outgoing request (to 
the server for which I am being a reverse-proxy) to match the incoming 
request in this regard, I wouldn't have enough information to know that I 
should do that.

Is there any way to get at the raw HTTP request so I can inspect it?  I 
think I need to see exactly how the client created it in the first place.

On Tuesday, September 13, 2016 at 12:58:15 PM UTC-4, Derek Wyatt wrote:
>
> 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 that using Akka HTTP.  I think we can all 
> agree that the addition of charset=UTF-8 is the right thing to do, but in 
> this case it may be causing us a problem and I'd like to force it to look 
> the same.  The best I've gotten so far is a definition where it has 
> 'charset=', which isn't quite right.
>
> Can this be done?
>

-- 
>>>>>>>>>>      Read the docs: http://akka.io/docs/
>>>>>>>>>>      Check the FAQ: 
>>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html
>>>>>>>>>>      Search the archives: https://groups.google.com/group/akka-user
--- 
You received this message because you are subscribed to the Google Groups "Akka 
User List" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

Reply via email to