Hi Florian, can you clarify what needs improvement? Is that about client or server side?
Johannes On Saturday, May 13, 2017 at 10:47:52 AM UTC+2, Florian Rosenberg wrote: > > I'm seeing a similar problem, but not wit the URI but with the > Strict-Transport-Header, it seems to be invalid, changing the conf to > ignore it has no effect. I'm using a websocket though. > > After debugging around for a while, I instrumented some code and see this: > > Illegal 'strict-transport-security' header: Invalid input 'EOI', expected > OWS, 'i' or token0 (line 1, column 18): max-age=31536000; > > It may well be that the endpoint I'm sending it to does not treat this > correctly and returns a 400 (Bad request), but I need to be able to ignore > this somehow. > -- >>>>>>>>>> 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.
