This bug report is being closed due to your last comment regarding this
being fixed with an update. For future reference you can manage the
status of your own bugs by clicking on the current status in the yellow
line and then choosing a new status in the revealed drop down box. You
can learn more a
This might be http://redmine.lighttpd.net/issues/657 .
--
updating from lighttpd w/ pipelining - connection reset
https://bugs.launchpad.net/bugs/47427
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bu
Er, you're aware that this bug was submitted in 2006, and the newest
comment is from 2008, right? I mean, I fully appreciate that you're
trying to reproduce and fix the issue but I for one no longer have the
setup in question.
--
updating from lighttpd w/ pipelining - connection reset
https://bug
Can you reproduce this issue on a more current Ubuntu installation?
I've tried to reproduce with lighty and failed to do so, but since you
say it is a 1% issue, perhaps I'm just not lucky enough :)
** Changed in: apt (Ubuntu)
Status: New => Incomplete
--
updating from lighttpd w/ pipelini
I encountered this bug on both feisty and gutsy (did not try on hardy
nor intrepid). The workaround worked for both. Thanks.
--
updating from lighttpd w/ pipelining - connection reset
https://bugs.launchpad.net/bugs/47427
You received this bug notification because you are a member of Ubuntu
Bugs,
