On Mon, Nov 1, 2010 at 10:37 AM, Tomas Doran wrote:
>
> On 1 Nov 2010, at 08:43, Felix Antonius Wilhelm Ostmann wrote:
>
> nothing? :-/
>>
>> Am 04.10.2010 10:16, schrieb Felix Antonius Wilhelm Ostmann:
>>
>>> It there a plan to change this error?
>>>
>>
> I'd love someone to make some patches i
On 1 Nov 2010, at 08:43, Felix Antonius Wilhelm Ostmann wrote:
nothing? :-/
Am 04.10.2010 10:16, schrieb Felix Antonius Wilhelm Ostmann:
It there a plan to change this error?
I'd love someone to make some patches in a branch :)
Cheers
t0m
___
L
nothing? :-/
Am 04.10.2010 10:16, schrieb Felix Antonius Wilhelm Ostmann:
> It there a plan to change this error?
>
> Am 29.09.2010 06:39, schrieb Aristotle Pagaltzis:
>> * Bill Moseley [2010-09-08 23:15]:
>>> Shouldn't that just return 411, 413, or just a 400?
>>
>> Returning 411 is indeed exac
It there a plan to change this error?
Am 29.09.2010 06:39, schrieb Aristotle Pagaltzis:
> * Bill Moseley [2010-09-08 23:15]:
>> Shouldn't that just return 411, 413, or just a 400?
>
> Returning 411 is indeed exactly what the server should do.
> (413 is wrong. 400 is fine but not as helpful.) The
* Bill Moseley [2010-09-08 23:15]:
> Shouldn't that just return 411, 413, or just a 400?
Returning 411 is indeed exactly what the server should do.
(413 is wrong. 400 is fine but not as helpful.) The server should
definitely not throw an error. It shouldn’t even log a warning,
because this has no
Am 14.09.2010 01:02, schrieb Bill Moseley:
> I need a smarter system where the logs get filtered by an external
> process that can be updated dynamically with filters. After I see 100
> similar messages I can probably afford to suppress that message so other
> more important messages don't get los
On Wed, Sep 8, 2010 at 2:08 PM, Bill Moseley 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
> for an error nobody can fix.
>
"Wrong Content-Length value: $length"
I've received hund
