couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jan Lehnardt (JIRA)" <j...@apache.org>
Subject [jira] Closed: (COUCHDB-367) CouchDB caching attachments that have been overwritten
Date Wed, 02 Jun 2010 20:31:40 GMT

     [ https://issues.apache.org/jira/browse/COUCHDB-367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jan Lehnardt closed COUCHDB-367.
--------------------------------

    Resolution: Cannot Reproduce

Can't reproduce in 0.11.0 or later. Please reopen if this issue persists.

> CouchDB caching attachments that have been overwritten
> ------------------------------------------------------
>
>                 Key: COUCHDB-367
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-367
>             Project: CouchDB
>          Issue Type: Bug
>    Affects Versions: 0.9
>         Environment: 64-bit Linux (Fedora 11) 2.6.29.4-162.fc11.x86_64 #1 SMP
> Erlang (BEAM) emulator version 5.6.5 [source] [64-bit] [smp:4] [async-threads:0] [hipe]
[kernel-poll:false]
> CouchDB 0.9.0 (installed from the yum packages)
>            Reporter: Vilya Harvey
>
> I created a document with an image file as an attachment, then replaced the attachment
with a different image. CouchDB still serves the older image instead of the replacement.
> Steps to recreate:
> 1. Create a new document.
> 2. Using Futon, upload an image called "test.jpg" as an attachment to the document.
> 3. View the attachment to confirm that it's uploaded correctly.
> 4. Back in Futon, upload a different image with the same filename ("test.jpg") as an
attachment to the document. Futon will correctly report the size of the new attachment.
> 5. View the attachment - you will still see the image from step 2.
> 6. View the attachment in a different web browser, to make sure it's not just browser
caching. You will still see the image from step 2 instead of the newer one.
> BTW I came across this because I was doing some experiments to see whether CouchDB would
keep the attachment revision history for me. So if the above is the wrong way to create a
new version of an attachment, I apologise now!

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message