[
http://jira.codehaus.org/browse/WAGON-119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg closed WAGON-119.
-------------------------------
Resolution: Won't Fix
Fix Version/s: (was: 1.x)
Assignee: Mark Struberg
Not sure if that would really pay off.
Maven has an own update policy in the <repository> section anyway. So it will
not perform a GET if the resource already got downloaded before and did fall in
that time frame. We would need to really tweak lots of things like the -U
option etc to pass this info through correctly
<repository>
<id>myrepo</id>
<name>my repository</name>
<url>http://myrepo.com</url>
<snapshots>
<enabled>false</enabled>
<updatePolicy>interval:60</updatePolicy>
</snapshots>
</repository>
will only check for updates after the artifact didn't get resolved for 60
minutes.
> Use Pragma: no-cache only when appropriate
> ------------------------------------------
>
> Key: WAGON-119
> URL: http://jira.codehaus.org/browse/WAGON-119
> Project: Maven Wagon
> Issue Type: Improvement
> Components: wagon-http
> Environment: Maven 2.0.4, Mac OS X 10.4.6
> Reporter: Gordon Henriksen
> Assignee: Mark Struberg
>
> Maven issues all of its HTTP GET requests with a Pragma: no-cache field in
> the header. This makes it impossible to use a caching reverse proxy in lieu
> of a complete ibiblio mirror.
> Brett notes:
> > It should actually be something that is configured on the wagon.get()
> > request, actually, so that Maven could send it for snapshots and
> > metadata, but not others. But a global setting should be ok too if the
> > proxy owner knows what they are doing.
> I'm not much attached to a global configuration switch to globally disable
> the option, since Maven knows more about its usage than the proxy possibly
> can. Nonetheless, very few, if any, requests to ibiblio should be marked as
> no-cache.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
