agree - seems to warrant more of a 'warn' than 'error'. On Wed, Sep 8, 2010 at 4:59 PM, Bill Moseley <[email protected]> wrote:
> > > On Wed, Sep 8, 2010 at 4:13 PM, Nicholas Wehr <[email protected] > > wrote: > >> okay - in this context I can understand your original message. I think >> catalyst is behaving okay. In your example, the client is disconnected so it >> cannot receive a response code. in my test telnet where I ran your example, >> I fed more data in than was expected - but since I left the client connected >> I got a response. the server went ahead and detected the content-length and >> failed gracefully, though cryptically... > > > Correct, because it only checks: > > if ( $remaining > 0 ) { > > Not sure why it's ok for the Content-Length to be less than the actual > content and not the other way around. > > Regardless, my question was just is this the level of an error? Do we > really care if a request is disconnected? > > I can downgrade the message to a warn in my logging code to avoid getting > emails about it every few hours. > > > -- > Bill Moseley > [email protected] > > _______________________________________________ > List: [email protected] > Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst > Searchable archive: > http://www.mail-archive.com/[email protected]/ > Dev site: http://dev.catalyst.perl.org/ > >
_______________________________________________ List: [email protected] Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/[email protected]/ Dev site: http://dev.catalyst.perl.org/
