Bug#691600: [Pkg-haskell-maintainers] Bug#691600: libghc-warp-dev: does not parse request headers correctly

2012-10-27 Thread YOSHINO Yoshihito
Hi, On Sat, Oct 27, 2012 at 11:31 PM, Joachim Breitner nome...@debian.org wrote: Version: 1.3.4.1-1 Am Samstag, den 27.10.2012, 22:36 +0900 schrieb YOSHINO Yoshihito: Upstream has fixed the issue (tracked in https://github.com/yesodweb/wai/issues/76) and released as warp 1.2.2 (while this

Bug#691600: [Pkg-haskell-maintainers] Bug#691600: libghc-warp-dev: does not parse request headers correctly

2012-10-27 Thread Joachim Breitner
Hi, Am Samstag, den 27.10.2012, 23:37 +0900 schrieb YOSHINO Yoshihito: On Sat, Oct 27, 2012 at 11:31 PM, Joachim Breitner nome...@debian.org wrote: Am Samstag, den 27.10.2012, 22:36 +0900 schrieb YOSHINO Yoshihito: Upstream has fixed the issue (tracked in

Bug#691600: [Pkg-haskell-maintainers] Bug#691600: libghc-warp-dev: does not parse request headers correctly

2012-10-27 Thread YOSHINO Yoshihito
Hi, On Sat, Oct 27, 2012 at 11:40 PM, Joachim Breitner nome...@debian.org wrote: I see. Can you elaborate on the severity of the problem? Do such request headers occur in common situations, or is it just a theoretical problem? Actually I have stuck in a warp server receiving request from

Bug#691600: [Pkg-haskell-maintainers] Bug#691600: libghc-warp-dev: does not parse request headers correctly

2012-10-27 Thread Joachim Breitner
Hi, Am Sonntag, den 28.10.2012, 00:14 +0900 schrieb YOSHINO Yoshihito: On Sat, Oct 27, 2012 at 11:40 PM, Joachim Breitner nome...@debian.org wrote: I see. Can you elaborate on the severity of the problem? Do such request headers occur in common situations, or is it just a theoretical