this is from a client email:

We discovered a strange behaviour uploading different versions of a file. Under certain circumstances non-current attachment versions cannot be accessed. This can be reproduced with a fresh new confluence 2.2.9 standalone install.

When uploading a file - say abc.txt - everything works fine.
Loading up the file again, it gets versioned and we have abc.txt and Version 1 of this file - fine as well.

Now, when one of the non-current versions is requested by a browser it is displayed. When we upload a new version of abc.txt after that, the new non-current version is not accessible any more. Instead an error page "The page you were trying to reach does not exist. You may want to try a search, or browse the site to find the page you were looking for." is displayed.
Restarting the server resolves the problem until next update of the file.

In short:

• upload abc.txt
• upload abc.txt again
• check version 1 with the browser
• upload abc.txt again
• check version 1 -> fine
• check version 2 -> it fails

Or, more general:

• upload abc.txt
• upload abc.txt again n times -> we have a current and n non-current versions
• check one of the n non-current versions with the browser
• upload abc.txt again
• check non-current versions 1 to n -> fine
• check new non-current version n+1 -> it fails

Uploading with the XML-RPC api, non of the non-current versions is displayed.

–