Revision 8b967bbc91260ba0b8422e5ebedb2a4df47db2c0 authored by Mark Nottingham on 24 February 2017, 07:19:25 UTC, committed by Anne van Kesteren on 24 February 2017, 07:19:25 UTC
Per Fetch and HTTP a 304 should be under the same CORS policy as the original 200 (unless it changes it). This is testing to make sure that this is the case, since many servers (including intermediaries) do NOT add CORS headers (and some can't -- e.g., intermediary caches).
1 parent 771007a
content_length.html
<!DOCTYPE html>
<!-- CAUTION: if updating this test also update the expected content-length in the .headers file -->
<title>Content-Length Test</title>
<script src="/resources/testharness.js"></script>
<script src="/resources/testharnessreport.js"></script>
<script>
onload = function() {
assert_equals(document.body.textContent, "PASS");
done();
}
</script>
<body>PASS
but FAIL if this is in the body.
Computing file changes ...
