<p>Under some circumstances, the server must spool request bodies
to disk to satisfy the requested handling of request bodies. For
example, this spooling will occur if the original body was sent with
- chunked encoding (and and is large), but the administrator has
+ chunked encoding (and is large), but the administrator has
asked for backend requests to be sent with Content-Length or as HTTP/1.0.
This spooling can also occur if the request body already has a
Content-Length header, but the server is configured to filter incoming
</div><div id="footer">
<p class="apache">Copyright 2010 The Apache Software Foundation.<br />Licensed under the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.</p>
<p class="menu"><a href="../mod/">Modules</a> | <a href="../mod/directives.html">Directives</a> | <a href="../faq/">FAQ</a> | <a href="../glossary.html">Glossary</a> | <a href="../sitemap.html">Sitemap</a></p></div>
-</body></html>
\ No newline at end of file
+</body></html>
<p>Under some circumstances, the server must spool request bodies
to disk to satisfy the requested handling of request bodies. For
example, this spooling will occur if the original body was sent with
- chunked encoding (and and is large), but the administrator has
+ chunked encoding (and is large), but the administrator has
asked for backend requests to be sent with Content-Length or as HTTP/1.0.
This spooling can also occur if the request body already has a
Content-Length header, but the server is configured to filter incoming