> "Remy Maucherat" <[EMAIL PROTECTED]> wrote: > > > > If people feel uncomfortable with the current behavior (although I assure > > you, it shouldn't break anything), we can change to <300 (many 3xx "need" > > status reports; at least, Apache give status reports for a lot of them, so I > > thought it was wise to do the same). > > I don't feel unconfortable until the AvantGo people don't call me up saying > that I'm screwing their whole HTTP stack. Coyote's 1.0-b8 actually fixes > that problem, I figured that out tonight in a rage of testing HTTPs but it's > damn broken in 4.0.4-b2 (NPEs following). I should have tried that out > first... > > I'd be more confortable though if we didn't touch anything below 400... > > Pier (NPE following now) > > ERROR] Http11Processor - -Error finishing response > <java.lang.NullPointerException> > java.lang.NullPointerException > at > org.apache.coyote.http11.InternalOutputBuffer.write(InternalOutputBuffer.jav > a:583) > at > org.apache.coyote.http11.InternalOutputBuffer.sendStatus(InternalOutputBuffe > r.java:411)
Well, yeah, that's a stupid NPE, which happens whenever the message text is null. When you call sendError(456, "Arg, broken") it worked, but using setStatus(456) left it null, which caused the bug. Easy fix :) Remy -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
