Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Websockets client and illegal headers #1166
Comments
jrudolph
added 0 - new bug 1 - triaged community and removed 0 - new
labels
May 30, 2017
|
Thanks for the report, @disblader. I can confirm that it is like you report. The reason is that in this line, the default |
|
Pardon my ignorance, but what's the process for having bugs like this fixed? Is someone from the community expected to pick this up and fix it? Should I try to do it myself and then do a pull request? |
|
As it is labelled with the Regarding how to contribute to Akka HTTP, you can go over the CONTRIBUTING file where the procedure is explained. |
|
Thanks! I'll get on it straight away. |
|
I think I got it, but I've got a couple of questions. First, I'm not sure how I should handle an unexpected value here. Is there an exception that implementors generally use for these kinds of situations? Secondly, I'm pretty bad with scalatest and I ended up in this situation where I have identical tests with different setups and I'm not sure if that's fine or not? |
|
I think it's better to discuss those on the PR directly. |
|
What I mean, is that you can submit the PR (you can name it WIP if you want) and add this comments there. |
|
Fair enough. I shall do so. Thanks! |
jrudolph
added 3 - in progress and removed 1 - triaged
labels
Jun 6, 2017
joan38
commented
Jun 7, 2017
•
|
I'm having this issue with the Kubernetes API:
|
asm123
commented
Jun 8, 2017
|
I am facing the same exception. Was anybody able to resolve it? |
|
I've made a fix for it, it's currently sitting in #1175, there's a couple of final touches needed and it'll probably be merged in. As for a work-around I could not figure one out myself. |
2m
added a commit
that referenced
this issue
Jun 19, 2017
|
|
disblader + 2m |
e56661d
|
johanandren commentedMay 26, 2017
Moving it over from akka/akka#23026 reported by @disblader
Hello,
It seems that illegal headers crash the websocket client flow.
I am trying to connect to a websocket server which sends a server header containing a semicolon (e.g. "server: something; something"). When attempting to connect, akka seems to die. The log:
To reproduce, run
{ echo -ne "HTTP/1.0 200 OK\r\nServer: something; something\r\nContent-Length: 10\r\n\r\n1111111111"; } | nc -l 8080, and then run the following codeI also tried to change
akka.http.parsing.illegal-response-header-value-processing-modeto try and circumvent this issue. It does not seem to have worked, however. I can see that it works when making regular HTTP requests, but it seems to have no effect on the websocket requests. Is there anything else that can be done?