Re: [fetch-tests] fetch conditional GET with ETags [WIP] (#3592)

> the main problem with this test is that it only works once

Perhaps I'm misunderstanding you, but it's not supposed to work at all: This test case is supposed to illustrate what seems like a bug in browser implementations (see description above), so it's should be failing:

```javascript
// runner-results.json
{
  "results": [
    {
      "test": "/fetch/bugs/request-etag.html",
      "subtests": [
        {
          "name": "Testing ETag handling",
          "status": "FAIL",
          "message": "assert_equals: expected 304 but got 200"
        }
      ],
      "status": "OK",
      "message": null
    }
  ]
}
```
(just confirmed again; I've updated OP's browser versions accordingly)

> It's somewhat similar to fetch/api/request/request-cache.html actually. Maybe this is already tested there?

Unfortunately, I couldn't definitively decipher what's going on there (too much abstraction). But while it does seem to test something similar, it didn't exhibit the issue I was observing (see above), so there's some sort of mismatch here.

View on GitHub: https://github.com/w3c/web-platform-tests/pull/3592#issuecomment-248313529

Received on Tuesday, 20 September 2016 14:14:07 UTC