[jira] Commented: (COUCHDB-929) jsonp test fails with '1. Assertion failed: xhr.status == 400'

["Hrunting Johnson (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/COUCHDB-929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12926732#action_12926732 ] 

Hrunting Johnson commented on COUCHDB-929:
------------------------------------------

Chrome's 200 response it reports looks to also be the result of receiving a 304 from the server.

> jsonp test fails with '1. Assertion failed: xhr.status == 400'
> --------------------------------------------------------------
>
>                 Key: COUCHDB-929
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-929
>             Project: CouchDB
>          Issue Type: Bug
>          Components: Test Suite
>    Affects Versions: 1.0.1
>         Environment: Ubuntu Linux 10.10
>            Reporter: Hrunting Johnson
>
> The jsonp test fails with '1. Assertion failed: xhr.status == 400' reproducibly every time.
> When running the test under Firefox, it's the last xhr.status check that fails, which is a GET of the following URL:
> /test_suite_db/_design/test/_view/all_docs?callback=jsonp_chunk'
> Firebug reports that the URL fetched is:
> /test_suite_db/_design/test/_view/all_docs?callback=jsonp_chunk%27
> When running under Chrome, it's the first xhr.status check that fails, which is a GET of the following URL:
> /test_suite_db/0?callback=foo"
> In both cases, the test expects to receive a status code of 400 and gets a status code of 200.  Firefox appears to be failing because it's actually getting back a 304 Not Modified and using a cached result.  Chrome is getting back a 200 response from the server with an actual JSON result.

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