You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Notice the colon after www.google.de:. It works if there is a port number after the colon www.google.de:443.
The message is Could not parse data entirely (22 != 100) and the colon is the 22nd char.
I realise that the message above is probably malformed, but I'm not sure about that as I didn't find the relevant RFC yet. Still as we try to be robust in what data we accept, I could see this being accepted by http_parser.rb. What do you think?
The text was updated successfully, but these errors were encountered:
A client sends this request:
Notice the colon after
www.google.de:
. It works if there is a port number after the colonwww.google.de:443
.The message is
Could not parse data entirely (22 != 100)
and the colon is the 22nd char.I realise that the message above is probably malformed, but I'm not sure about that as I didn't find the relevant RFC yet. Still as we try to be robust in what data we accept, I could see this being accepted by
http_parser.rb
. What do you think?The text was updated successfully, but these errors were encountered: