You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by ji...@codehaus.org on 2004/03/07 00:55:28 UTC

[jira] Updated: (MAVEN-1188) SNAPSHOT downloading subject to race conditions

The following issue has been updated:

    Updater: Brett Porter (mailto:brett@codehaus.org)
       Date: Sat, 6 Mar 2004 6:54 PM
    Changes:
             Fix Version changed to 1.0-final
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1188&page=history

---------------------------------------------------------------------
View the issue:
  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1188

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: MAVEN-1188
    Summary: SNAPSHOT downloading subject to race conditions
       Type: Bug

     Status: Unassigned
   Priority: Major

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

    Project: maven
 Components: 
             core
   Fix Fors:
             1.0-final

   Assignee: 
   Reporter: Ben Walding

    Created: Thu, 4 Mar 2004 8:58 PM
    Updated: Sat, 6 Mar 2004 6:54 PM

Description:
When downloading snapshots, we use the If-Modified-Since header.  The rules for this header state (from the http1.1 spec)

14.25 If-Modified-Since
...
a) If the request would normally result in anything other than a
200 (OK) status, or if the passed If-Modified-Since date is
invalid, the response is exactly the same as for a normal GET.
A date which is later than the server's current time is
invalid.

Note the last line : "A date which is later than the server's current time is invalid."

Now if you just built a snapshot in one project, then move onto another that uses it, there is a chance
that your If-Modified-Since header is ahead of ibiblio / your upstream server.

Thus, the full SNAPSHOT is downloaded over the top of the existing one - even though the
upstream server is in fact serving up an older copy of the snapshot.

I've tested this on hogshead vs. ibiblio and it is what is causing the problem - hogshead time was
30 minutes faster than ibiblio, so my fresh snapshots were getting overwritten by ibiblio's old one.
(hogshead was sending a header that was in the future to ibiblio - and thus ignored).



---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org