Re: [Catalyst] Wrong Content-Length value

2010-09-09 Thread Felix Antonius Wilhelm Ostmann
see here: https://rt.cpan.org/Public/Bug/Display.html?id=53226 Am 09.09.2010 02:03, schrieb Nicholas Wehr: agree - seems to warrant more of a 'warn' than 'error'. On Wed, Sep 8, 2010 at 4:59 PM, Bill Moseley mose...@hank.org mailto:mose...@hank.org wrote: On Wed, Sep 8, 2010 at

Re: [Catalyst] Wrong Content-Length value

2010-09-09 Thread Felix Antonius Wilhelm Ostmann
We have exactly the same problem. Every error triggers emails to the dev-team. And this occure ~20 times a day. Perhaps it is not paranoid and a simple 410 (or similar) will be a better answer without sending errors to the app? Am 09.09.2010 01:59, schrieb Bill Moseley: On Wed, Sep 8, 2010

[Catalyst] Wrong Content-Length value

2010-09-08 Thread Bill Moseley
The problem I have with this code is that requests can trigger an error on demand. Errors eventually trigger an email to a bunch of people. But it's for an error nobody can fix. # paranoia against wrong Content-Length header my $remaining = $length - $self-read_position;

Re: [Catalyst] Wrong Content-Length value

2010-09-08 Thread Nicholas Wehr
so which engine and version are you using? apache? built-in http? fastcgi? On Wed, Sep 8, 2010 at 2:08 PM, Bill Moseley mose...@hank.org wrote: The problem I have with this code is that requests can trigger an error on demand. Errors eventually trigger an email to a bunch of people. But it's

Re: [Catalyst] Wrong Content-Length value

2010-09-08 Thread Bill Moseley
On Wed, Sep 8, 2010 at 2:16 PM, Nicholas Wehr catal...@bionikchickens.comwrote: so which engine and version are you using? apache? built-in http? fastcgi? Apache, but that message is in Catalyst::Engine parent class. -- Bill Moseley mose...@hank.org

Re: [Catalyst] Wrong Content-Length value

2010-09-08 Thread Nicholas Wehr
interesting problem. so the client is making byte-range requests on dynamic content? if it's static - I'd recommend you defer this functionality to apache. On Wed, Sep 8, 2010 at 2:30 PM, Bill Moseley mose...@hank.org wrote: On Wed, Sep 8, 2010 at 2:16 PM, Nicholas Wehr

Re: [Catalyst] Wrong Content-Length value

2010-09-08 Thread Ashley Pond V
On Wed, Sep 8, 2010 at 2:30 PM, Bill Moseley mose...@hank.org wrote: On Wed, Sep 8, 2010 at 2:16 PM, Nicholas Wehr catal...@bionikchickens.com wrote: so which engine and version are you using? apache? built-in http? fastcgi? Apache, but that message is in Catalyst::Engine parent class.

Re: [Catalyst] Wrong Content-Length value

2010-09-08 Thread Bill Moseley
On Wed, Sep 8, 2010 at 2:38 PM, Nicholas Wehr catal...@bionikchickens.comwrote: interesting problem. so the client is making byte-range requests on dynamic content? if it's static - I'd recommend you defer this functionality to apache. No, it's not that. It's simply that the client is

Re: [Catalyst] Wrong Content-Length value

2010-09-08 Thread Nicholas Wehr
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

Re: [Catalyst] Wrong Content-Length value

2010-09-08 Thread Bill Moseley
On Wed, Sep 8, 2010 at 4:13 PM, Nicholas Wehr catal...@bionikchickens.comwrote: 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

Re: [Catalyst] Wrong Content-Length value

2010-09-08 Thread Nicholas Wehr
agree - seems to warrant more of a 'warn' than 'error'. On Wed, Sep 8, 2010 at 4:59 PM, Bill Moseley mose...@hank.org wrote: On Wed, Sep 8, 2010 at 4:13 PM, Nicholas Wehr catal...@bionikchickens.com wrote: okay - in this context I can understand your original message. I think catalyst is

[Catalyst] Wrong Content-Length value: 392918

2010-06-08 Thread Bill Moseley
I see these errors a few times a day. I wonder why this is happening -- could the browser really send the wrong content length? I seem to see it often in ajax calls for a progress bar, but also during file uploads and sometimes for just a normal post. Is there any additional info that could be