https://bz.apache.org/bugzilla/show_bug.cgi?id=65340
--- Comment #14 from Thomas ---
I think they are not the same issue. The issue you mentioned above is also
submitted by me. The same time, I had submitted the same one in tomcat as
follow:
https://bz.apache.org/bugzilla/show_bug.cgi?id=65350
https://bz.apache.org/bugzilla/show_bug.cgi?id=65340
--- Comment #13 from Joakim Erdfelt ---
Does this HPACK fix also address the HPACK index issue reported (at the Jetty
issue tracker) against Tomcat?
https://github.com/eclipse/jetty.project/issues/6341
--
You are receiving this mail
https://bz.apache.org/bugzilla/show_bug.cgi?id=65340
Remy Maucherat changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bz.apache.org/bugzilla/show_bug.cgi?id=65340
--- Comment #11 from Remy Maucherat ---
This is correct, the original code has the fix now. I'll do that.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bz.apache.org/bugzilla/show_bug.cgi?id=65340
--- Comment #10 from Thomas ---
I have reproduced the issue, please see the detail as below.
Reason description:
When the length of one header value is greater than 127 and its first prefix
byte is the last one in
https://bz.apache.org/bugzilla/show_bug.cgi?id=65340
linking12 <297442...@qq.com> changed:
What|Removed |Added
Priority|P2 |P1
https://bz.apache.org/bugzilla/show_bug.cgi?id=65340
--- Comment #9 from linking12 <297442...@qq.com> ---
public class Constants {
static final int DEFAULT_HEADER_READ_BUFFER_SIZE = 1024;
}
we found some bug for DEFAULT_HEADER_READ_BUFFER_SIZE, when one header is
larger than 1024, the
https://bz.apache.org/bugzilla/show_bug.cgi?id=65340
--- Comment #8 from linking12 <297442...@qq.com> ---
(In reply to gr...@webtide.com from comment #5)
> Mark, I can't tell either if this is Jetty encoding or Tomcat decoding.
>
> If you want to write a test to do some jetty encodes and
https://bz.apache.org/bugzilla/show_bug.cgi?id=65340
--- Comment #7 from Thomas ---
(In reply to Thomas from comment #6)
> I found some information. Can you give me some answers?
> 1. If my header size is very big. Its length is bigger than 1024 after
> huffman encoding, the header will not be
https://bz.apache.org/bugzilla/show_bug.cgi?id=65340
--- Comment #6 from Thomas ---
I found some information. Can you give me some answers?
1. If my header size is very big. Its length is bigger than 1024 after huffman
encoding, the header will not be got.
2. The value of the variable "length"
https://bz.apache.org/bugzilla/show_bug.cgi?id=65340
--- Comment #5 from gr...@webtide.com ---
Mark, I can't tell either if this is Jetty encoding or Tomcat decoding.
If you want to write a test to do some jetty encodes and tomcate decodes, then
if you have a maven dependency on
https://bz.apache.org/bugzilla/show_bug.cgi?id=65340
--- Comment #4 from linking12 <297442...@qq.com> ---
this is issue happen on prod env, It diffcult to reproduce.
some request is ok, but some request is error;
it is very difficult to reproduce, and tcpdump also difficult.
the purpose of
https://bz.apache.org/bugzilla/show_bug.cgi?id=65340
Mark Thomas changed:
What|Removed |Added
Severity|critical|enhancement
--- Comment #3 from Mark
https://bz.apache.org/bugzilla/show_bug.cgi?id=65340
--- Comment #2 from Thomas ---
The original exception stack trace is as below in Tomcat source:
java.lang.NegativeArraySizeException: -1
at
java.base/java.lang.AbstractStringBuilder.(AbstractStringBuilder.java:86)
at
https://bz.apache.org/bugzilla/show_bug.cgi?id=65340
--- Comment #1 from linking12 <297442...@qq.com> ---
3: hpack decode error, headerName: device-info, value: �
device-info is a base64 string
--
You are receiving this mail because:
You are the assignee for the bug.
15 matches
Mail list logo
