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:05 AM, Mark Thomas wrote:
On 21/01/2011 17:57, Konstantin Kolinko wrote:
2011/1/21 Christopher Schultz<ch...@christopherschultz.net>:
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<Connector> called
allowCasualMultipartParsing whose default value is "false". Please see
BZ for details.
I propose to make the default for this setting "true" unless
STRICT_SERVLET_COMPLIANCE is set to TRUE.
Any comments?
Why is it on Connector? Won't it be better to have it on Context?
Per Context seems reasonable to me.
As far as defaults go, I'd rather non-spec compliant features were
disabled by default. That way users have to explicitly enable them and
can't complain about portability when they move their app to a different
container that doesn't have the feature.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
