You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@couchdb.apache.org by "Mark Hammond (JIRA)" <ji...@apache.org> on 2009/06/18 02:44:08 UTC

[jira] Created: (COUCHDB-386) conditional requests for attachments always return 304

conditional requests for attachments always return 304
------------------------------------------------------

                 Key: COUCHDB-386
                 URL: https://issues.apache.org/jira/browse/COUCHDB-386
             Project: CouchDB
          Issue Type: Improvement
          Components: HTTP Interface
         Environment: svn trunk
            Reporter: Mark Hammond
         Attachments: attachment_304.patch

If you make a conditional request for a document using the etag, you correctly get a 304 response.  If you try the same thing with an attachment you always get a 304.  Attaching a test case to demonstrate this.


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


[jira] Updated: (COUCHDB-386) conditional requests for attachments never return 304

Posted by "Mark Hammond (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/COUCHDB-386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mark Hammond updated COUCHDB-386:
---------------------------------

    Summary: conditional requests for attachments never return 304  (was: conditional requests for attachments always return 304)

> conditional requests for attachments never return 304
> -----------------------------------------------------
>
>                 Key: COUCHDB-386
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-386
>             Project: CouchDB
>          Issue Type: Improvement
>          Components: HTTP Interface
>         Environment: svn trunk
>            Reporter: Mark Hammond
>         Attachments: attachment_304.patch
>
>
> If you make a conditional request for a document using the etag, you correctly get a 304 response.  If you try the same thing with an attachment you always get a 304.  Attaching a test case to demonstrate this.

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


[jira] Updated: (COUCHDB-386) conditional requests for attachments never return 304

Posted by "Mark Hammond (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/COUCHDB-386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mark Hammond updated COUCHDB-386:
---------------------------------

    Description: 
If you make a conditional request for a document using the etag, you correctly get a 304 response.  If you try the same thing with an attachment you always get a 200.  Attaching a test case to demonstrate this.


  was:
If you make a conditional request for a document using the etag, you correctly get a 304 response.  If you try the same thing with an attachment you always get a 304.  Attaching a test case to demonstrate this.



> conditional requests for attachments never return 304
> -----------------------------------------------------
>
>                 Key: COUCHDB-386
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-386
>             Project: CouchDB
>          Issue Type: Improvement
>          Components: HTTP Interface
>         Environment: svn trunk
>            Reporter: Mark Hammond
>         Attachments: attachment_304.patch
>
>
> If you make a conditional request for a document using the etag, you correctly get a 304 response.  If you try the same thing with an attachment you always get a 200.  Attaching a test case to demonstrate this.

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


[jira] Updated: (COUCHDB-386) conditional requests for attachments always return 304

Posted by "Mark Hammond (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/COUCHDB-386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mark Hammond updated COUCHDB-386:
---------------------------------

    Attachment: attachment_304.patch

patch to the attachment tests which demonstrates the behaviour.

> conditional requests for attachments always return 304
> ------------------------------------------------------
>
>                 Key: COUCHDB-386
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-386
>             Project: CouchDB
>          Issue Type: Improvement
>          Components: HTTP Interface
>         Environment: svn trunk
>            Reporter: Mark Hammond
>         Attachments: attachment_304.patch
>
>
> If you make a conditional request for a document using the etag, you correctly get a 304 response.  If you try the same thing with an attachment you always get a 304.  Attaching a test case to demonstrate this.

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


[jira] Closed: (COUCHDB-386) conditional requests for attachments never return 304

Posted by "Chris Anderson (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/COUCHDB-386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris Anderson closed COUCHDB-386.
----------------------------------

    Resolution: Fixed

fixed in 792774

> conditional requests for attachments never return 304
> -----------------------------------------------------
>
>                 Key: COUCHDB-386
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-386
>             Project: CouchDB
>          Issue Type: Improvement
>          Components: HTTP Interface
>         Environment: svn trunk
>            Reporter: Mark Hammond
>         Attachments: attachment_304.patch
>
>
> If you make a conditional request for a document using the etag, you correctly get a 304 response.  If you try the same thing with an attachment you always get a 200.  Attaching a test case to demonstrate this.

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