[Bug 66196] HTTP/1 connector doesn't blow-up when HTTP header contains non-ASCII characters

https://bz.apache.org/bugzilla/show_bug.cgi?id=66196 Mark Thomas changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|---

[Bug 66196] HTTP/1 connector doesn't blow-up when HTTP header contains non-ASCII characters

https://bz.apache.org/bugzilla/show_bug.cgi?id=66196 Mark Thomas changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED

[Bug 66196] HTTP/1 connector doesn't blow-up when HTTP header contains non-ASCII characters

https://bz.apache.org/bugzilla/show_bug.cgi?id=66196 --- Comment #11 from gabriel.holl...@appian.com --- Looking over the thread here, it sounded like the path forward was to log, and potentially drop the header for Http1.1 However that same change wasnt done for the AJP Processor, causing

[Bug 66196] HTTP/1 connector doesn't blow-up when HTTP header contains non-ASCII characters

https://bz.apache.org/bugzilla/show_bug.cgi?id=66196 --- Comment #10 from Julian Reschke --- > And then there is RFC 8187 that I don't think I have ever seen in real world > usage. Content-Disposition. Trust me. -- You are receiving this mail because: You are the assignee for the bug.

[Bug 66196] HTTP/1 connector doesn't blow-up when HTTP header contains non-ASCII characters

https://bz.apache.org/bugzilla/show_bug.cgi?id=66196 Mark Thomas changed: What|Removed |Added Resolution|--- |FIXED Status|NEW

[Bug 66196] HTTP/1 connector doesn't blow-up when HTTP header contains non-ASCII characters

https://bz.apache.org/bugzilla/show_bug.cgi?id=66196 Mark Thomas changed: What|Removed |Added CC||renaud.n...@gmail.com --- Comment #8

[Bug 66196] HTTP/1 connector doesn't blow-up when HTTP header contains non-ASCII characters

https://bz.apache.org/bugzilla/show_bug.cgi?id=66196 --- Comment #7 from Mark Thomas --- The first approved release with this change was 10.1.0. My current thinking is to allow another 2 to 3 releases before back-porting. -- You are receiving this mail because: You are the assignee for the

[Bug 66196] HTTP/1 connector doesn't blow-up when HTTP header contains non-ASCII characters

https://bz.apache.org/bugzilla/show_bug.cgi?id=66196 --- Comment #6 from ttera --- When will it be backported to v8.5, 9 and 10.0? -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe,

[Bug 66196] HTTP/1 connector doesn't blow-up when HTTP header contains non-ASCII characters

https://bz.apache.org/bugzilla/show_bug.cgi?id=66196 --- Comment #5 from Mark Thomas --- Fixed in 10.1.x for 10.1.0-M18 onwards I intend to delay back-porting for a few releases in case the changes to MessageBytes triggers regressions. -- You are receiving this mail because: You are the

[Bug 66196] HTTP/1 connector doesn't blow-up when HTTP header contains non-ASCII characters

https://bz.apache.org/bugzilla/show_bug.cgi?id=66196 --- Comment #4 from Boris Petrov --- Logging a warning (or even logging at the ERROR level) sounds great to me. Everyone should be monitoring their logs for warnings and errors so this should be visible to most. And would save people time as

[Bug 66196] HTTP/1 connector doesn't blow-up when HTTP header contains non-ASCII characters

https://bz.apache.org/bugzilla/show_bug.cgi?id=66196 Mark Thomas changed: What|Removed |Added Status|NEEDINFO|NEW --- Comment #3 from Mark Thomas

[Bug 66196] HTTP/1 connector doesn't blow-up when HTTP header contains non-ASCII characters

https://bz.apache.org/bugzilla/show_bug.cgi?id=66196 --- Comment #2 from Boris Petrov --- Well, in my case it was the `ETag` header but I believe it's illegal to send non-ASCII characters in any header. -- You are receiving this mail because: You are the assignee for the bug.

[Bug 66196] HTTP/1 connector doesn't blow-up when HTTP header contains non-ASCII characters

https://bz.apache.org/bugzilla/show_bug.cgi?id=66196 Mark Thomas changed: What|Removed |Added Status|NEW |NEEDINFO --- Comment #1 from Mark