I'd opt for the default value to be true. I rather have usability than
spec compliance.
that's exactly what the STRICT_SERVLET_COMPLIANCE flag does, it opts for
usability,performance etc rather than spec compliance, and the default
value I believe is false on that flag.
Filip
On 01/21/2011 11
2011/1/21 Christopher Schultz :
> What about it's default setting?
>
I would opt for "false"
1) on the same grounds as Mark
2) what will happen with an older application that itself implements
file upload if this feature were enabled globally?
+e.printStackTrace();
Us
Konstantin,
On 1/21/2011 12:57 PM, Konstantin Kolinko wrote:
> 2011/1/21 Christopher Schultz :
>> All,
>>
>> I've just committed a fix for
>> https://issues.apache.org/bugzilla/show_bug.cgi?id=49711
>> (HttpServletRequest#getParts() does not work in a Filter) with a new
>> configuration attribute
On 21/01/2011 17:57, Konstantin Kolinko wrote:
> 2011/1/21 Christopher Schultz :
>> All,
>>
>> I've just committed a fix for
>> https://issues.apache.org/bugzilla/show_bug.cgi?id=49711
>> (HttpServletRequest#getParts() does not work in a Filter) with a new
>> configuration attribute on the called
2011/1/21 Christopher Schultz :
> All,
>
> I've just committed a fix for
> https://issues.apache.org/bugzilla/show_bug.cgi?id=49711
> (HttpServletRequest#getParts() does not work in a Filter) with a new
> configuration attribute on the called
> allowCasualMultipartParsing whose default value is "f
