[jira] Updated: (GERONIMO-2343) tomcat does not use maxPostSize set in config.xml
[ http://issues.apache.org/jira/browse/GERONIMO-2343?page=all ]
Donald Woods updated GERONIMO-2343:
---
Fix Version/s: 1.1.2
1.2
Affects Version/s: 1.1
1.2
(was: 1.1.x)
tomcat does not use maxPostSize set in config.xml
-
Key: GERONIMO-2343
URL: http://issues.apache.org/jira/browse/GERONIMO-2343
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Components: Tomcat
Affects Versions: 1.2, 1.1, 1.1.1, 1.1.2
Reporter: Krishnakumar B
Fix For: 1.1.2, 1.2
Attachments: tomcat-maxPostSize.patch
I set a value for maxPostSize in config.xml
gbean name=TomcatWebConnector
attribute name=host0.0.0.0/attribute
attribute name=port8080/attribute
attribute name=redirectPort8443/attribute
attribute name=bufferSizeBytes2048/attribute
attribute name=maxThreads150/attribute
attribute name=acceptQueueSize100/attribute
attribute name=lingerMillis-1/attribute
attribute name=tcpNoDelaytrue/attribute
attribute name=minSpareThreads25/attribute
attribute name=maxSpareThreads75/attribute
attribute name=maxHttpHeaderSizeBytes8192/attribute
attribute name=hostLookupEnabledfalse/attribute
attribute name=connectionTimeoutMillis2/attribute
attribute name=uploadTimeoutEnabledfalse/attribute
attribute name=maxPostSize20/attribute
attribute name=maxSavePostSize4096/attribute
attribute name=emptySessionPathfalse/attribute
/gbean
Tomcat Connector uses the value set in Connector to check for POST size.
if (len 0) {
int maxPostSize = connector.getMaxPostSize();
if ((maxPostSize 0) (len maxPostSize)) {
context.getLogger().info
(sm.getString(coyoteRequest.postTooLarge));
throw new IllegalStateException(Post too large);
}
While in Connector GBean setAttribute does not set in Connector
connector.setAttribute(maxPostSize, new Integer(bytes));
This is set in hashtable in HTTP11Protocol Handler. As a result the default
value is maintained in connector ( 2097152 )
This fix uses setter method in connector to set this value. (
connector.setMaxPostSize(bytes) )
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-2343) tomcat does not use maxPostSize set in config.xml
[ http://issues.apache.org/jira/browse/GERONIMO-2343?page=all ]
Krishnakumar B updated GERONIMO-2343:
-
Affects Version/s: 1.1.1
tomcat does not use maxPostSize set in config.xml
-
Key: GERONIMO-2343
URL: http://issues.apache.org/jira/browse/GERONIMO-2343
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Components: Tomcat
Affects Versions: 1.1.1, 1.1.x, 1.1.2
Reporter: Krishnakumar B
Attachments: tomcat-maxPostSize.patch
I set a value for maxPostSize in config.xml
gbean name=TomcatWebConnector
attribute name=host0.0.0.0/attribute
attribute name=port8080/attribute
attribute name=redirectPort8443/attribute
attribute name=bufferSizeBytes2048/attribute
attribute name=maxThreads150/attribute
attribute name=acceptQueueSize100/attribute
attribute name=lingerMillis-1/attribute
attribute name=tcpNoDelaytrue/attribute
attribute name=minSpareThreads25/attribute
attribute name=maxSpareThreads75/attribute
attribute name=maxHttpHeaderSizeBytes8192/attribute
attribute name=hostLookupEnabledfalse/attribute
attribute name=connectionTimeoutMillis2/attribute
attribute name=uploadTimeoutEnabledfalse/attribute
attribute name=maxPostSize20/attribute
attribute name=maxSavePostSize4096/attribute
attribute name=emptySessionPathfalse/attribute
/gbean
Tomcat Connector uses the value set in Connector to check for POST size.
if (len 0) {
int maxPostSize = connector.getMaxPostSize();
if ((maxPostSize 0) (len maxPostSize)) {
context.getLogger().info
(sm.getString(coyoteRequest.postTooLarge));
throw new IllegalStateException(Post too large);
}
While in Connector GBean setAttribute does not set in Connector
connector.setAttribute(maxPostSize, new Integer(bytes));
This is set in hashtable in HTTP11Protocol Handler. As a result the default
value is maintained in connector ( 2097152 )
This fix uses setter method in connector to set this value. (
connector.setMaxPostSize(bytes) )
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-2343) tomcat does not use maxPostSize set in config.xml
[ http://issues.apache.org/jira/browse/GERONIMO-2343?page=all ]
Krishnakumar B updated GERONIMO-2343:
-
Attachment: tomcat-maxPostSize.patch
tomcat does not use maxPostSize set in config.xml
-
Key: GERONIMO-2343
URL: http://issues.apache.org/jira/browse/GERONIMO-2343
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Components: Tomcat
Affects Versions: 1.1.2, 1.1.x
Reporter: Krishnakumar B
Attachments: tomcat-maxPostSize.patch
I set a value for maxPostSize in config.xml
gbean name=TomcatWebConnector
attribute name=host0.0.0.0/attribute
attribute name=port8080/attribute
attribute name=redirectPort8443/attribute
attribute name=bufferSizeBytes2048/attribute
attribute name=maxThreads150/attribute
attribute name=acceptQueueSize100/attribute
attribute name=lingerMillis-1/attribute
attribute name=tcpNoDelaytrue/attribute
attribute name=minSpareThreads25/attribute
attribute name=maxSpareThreads75/attribute
attribute name=maxHttpHeaderSizeBytes8192/attribute
attribute name=hostLookupEnabledfalse/attribute
attribute name=connectionTimeoutMillis2/attribute
attribute name=uploadTimeoutEnabledfalse/attribute
attribute name=maxPostSize20/attribute
attribute name=maxSavePostSize4096/attribute
attribute name=emptySessionPathfalse/attribute
/gbean
Tomcat Connector uses the value set in Connector to check for POST size.
if (len 0) {
int maxPostSize = connector.getMaxPostSize();
if ((maxPostSize 0) (len maxPostSize)) {
context.getLogger().info
(sm.getString(coyoteRequest.postTooLarge));
throw new IllegalStateException(Post too large);
}
While in Connector GBean setAttribute does not set in Connector
connector.setAttribute(maxPostSize, new Integer(bytes));
This is set in hashtable in HTTP11Protocol Handler. As a result the default
value is maintained in connector ( 2097152 )
This fix uses setter method in connector to set this value. (
connector.setMaxPostSize(bytes) )
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
