SOLR-4265: Remove useless setting in Jetty's server config file, as maximum form content is now handled by solr's RequestParser and not the web container.

git-svn-id: https://svn.apache.org/repos/asf/lucene/dev/trunk@1429822 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Uwe Schindler 2013-01-07 14:42:45 +00:00
parent c446098665
commit b56b6c1f71
2 changed files with 0 additions and 13 deletions

View File

@ -5,6 +5,4 @@
<Set name="war"><SystemProperty name="jetty.home"/>/webapps/solr.war</Set>
<Set name="defaultsDescriptor"><SystemProperty name="jetty.home"/>/etc/webdefault.xml</Set>
<Set name="tempDirectory"><Property name="jetty.home" default="."/>/solr-webapp</Set>
<!-- Increase the maximum POST size to 1 MB to be able to handle large shard requests -->
<Set name="maxFormContentSize">1000000</Set>
</Configure>

View File

@ -12,17 +12,6 @@
<Configure id="Server" class="org.eclipse.jetty.server.Server">
<!-- Increase the maximum POST size to 1 MB to be able to handle large shard requests -->
<!-- allthough documented as the correct way to set the max POST size for
all webapps in a single server, this doesn't actaully work.
So instead it is set on the WebAppContext.
-->
<!--
<Call name="setAttribute">
<Arg>org.eclipse.jetty.server.Request.maxFormContentSize</Arg>
<Arg>1000000</Arg>
</Call>
-->
<!-- =========================================================== -->
<!-- Server Thread Pool -->
<!-- =========================================================== -->