Author: jdcasey
Date: Tue Jun 30 00:22:28 2009
New Revision: 789503
URL: http://svn.apache.org/viewvc?rev=789503&view=rev
Log:
Update docs to remove reference to deprecated configuration, in favor of
referencing it as generally supported configuration options. Leaving discussion
about default http headers a little non-specific since it's unclear whether the
default caching headers can be turned off.
Modified:
maven/site/trunk/src/site/apt/guides/mini/guide-http-settings.apt
Modified: maven/site/trunk/src/site/apt/guides/mini/guide-http-settings.apt
URL:
http://svn.apache.org/viewvc/maven/site/trunk/src/site/apt/guides/mini/guide-http-settings.apt?rev=789503&r1=789502&r2=789503&view=diff
==============================================================================
--- maven/site/trunk/src/site/apt/guides/mini/guide-http-settings.apt (original)
+++ maven/site/trunk/src/site/apt/guides/mini/guide-http-settings.apt Tue Jun
30 00:22:28 2009
@@ -262,15 +262,15 @@
the one used by the client to access the server. If you have this problem,
and know that you don't need to use
this session cookie, you can ignore cookies from this server with the above
configuration.
-*Deprecation Notes
+*Support for General-Wagon Configuration Standards
- It should be noted that configuration options previously available in the
HttpClient-driven HTTP wagon have been
- deprecated in favor of this more general, fine-grained approach. These
include the configuration of HTTP headers
+ It should be noted that configuration options previously available in the
HttpClient-driven HTTP wagon are still
+ supported in addition to this new, fine-grained approach. These include the
configuration of HTTP headers
and connection timeouts. Let's examine each of these briefly:
**HTTP Headers
- Previously, you could add your own HTTP headers to the HttpClient-based
wagon like this:
+ In all HTTP Wagon implementations, you can add your own HTTP headers like
this:
+---+
<settings>
@@ -290,8 +290,9 @@
</settings>
+---+
- It's important to understand that the above method didn't allow you to turn
off the default HTTP headers; nor
- did it allow you to specify headers on a per-method basis.
+ It's important to understand that the above approach doesn't allow you to
turn off all of the default HTTP headers; nor
+ does it allow you to specify headers on a per-method basis. However, this
configuration remains available in both the
+ lightweight and httpclient-based Wagon implementations.
**Connection Timeouts
