HTTP chunk decoding question
22 views
Skip to first unread message
Julien Viet
Apr 16, 2018, 4:30:59 AM4/16/18
to ne...@googlegroups.com
Hi,
I'm looking at HTTP chunked decoding bug reported by the community in Vert.x
One bug concerns an invalid chunk size with a missing new line after the chunk size
so instead of
"4\r\n not\r\n"
the chunk is
"4 not\r\n"
which is accepted by Netty decoder because of the whitespace after the digit.
I've checked the HttpObjectDecoder and the reason why it accepts it is that the whitespace seems considered as equals as ";" for encoding extensions.
the HTTP 1.1 spec for chunked mentions that extensions begins with ";"
any explanation for this to be valid ?
Julien
I'm looking at HTTP chunked decoding bug reported by the community in Vert.x
One bug concerns an invalid chunk size with a missing new line after the chunk size
so instead of
"4\r\n not\r\n"
the chunk is
"4 not\r\n"
which is accepted by Netty decoder because of the whitespace after the digit.
I've checked the HttpObjectDecoder and the reason why it accepts it is that the whitespace seems considered as equals as ";" for encoding extensions.
the HTTP 1.1 spec for chunked mentions that extensions begins with ";"
any explanation for this to be valid ?
Julien
Norman Maurer
May 16, 2018, 2:20:38 PM5/16/18
to Netty discussions
Sorry I totally missed this one.
This does sounds like a bug. Can you open one ?
Julien Viet
Jun 1, 2018, 3:40:31 PM6/1/18
to ne...@googlegroups.com
totally missed your reply :-)
yes I will and contribute something.
--
You received this message because you are subscribed to the Google Groups "Netty discussions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to netty+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/netty/f96ae0c6-4281-40b7-87ca-7e34ab34ab97%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply all
Reply to author
Forward
0 new messages