first commit

Author: mnot

.editorconfig

@@ -0,0 +1,17 @@
+root = true
+
+# Unix-style newlines with a newline ending every file
+[*]
+end_of_line = lf
+insert_final_newline = true
+indent_style = space
+charset = utf-8
+trim_trailing_whitespace
+max_line_length = 100
+indent_size = 2
+
+[*.py]
+indent_size = 4
+
+[Makefile]
+indent_style = tab

LICENSE

@@ -0,0 +1,29 @@
+BSD 3-Clause License
+
+Copyright (c) 2018, Mark Nottingham
+All rights reserved.
+
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions are met:
+
+* Redistributions of source code must retain the above copyright notice, this
+  list of conditions and the following disclaimer.
+
+* Redistributions in binary form must reproduce the above copyright notice,
+  this list of conditions and the following disclaimer in the documentation
+  and/or other materials provided with the distribution.
+
+* Neither the name of the copyright holder nor the names of its
+  contributors may be used to endorse or promote products derived from
+  this software without specific prior written permission.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
+AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE
+FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
+SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
+CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
+OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
+OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

Makefile

@@ -0,0 +1,8 @@
+
+.PHONY: server
+server:
+	node server.js
+	
+.PHONY: lint
+lint:
+	standard --fix server.js client.js utils.js templates.js tests/*.js

README.md

@@ -0,0 +1,86 @@
+# CDN Tests
+
+These tests cover HTTP-specified behaviours for CDNs, primarily from
+[RFC7234](http://httpwg.org/specs/rfc7234.html), but as seen through the lens of
+[Fetch](https://fetch.spec.whatwg.org/).
+
+A few notes:
+
+* By its nature, caching is optional; some tests expecting a response to be cached might fail
+  because the client chose not to cache it, or chose to race the cache with a network request.
+
+* Likewise, some tests might fail because there is a separate document-level cache that's
+  ill-defined; see [this issue](https://github.com/whatwg/fetch/issues/354).
+
+* Some browser caches will behave differently when reloading / shift-reloading, despite the `cache
+  mode` staying the same.
+
+* They only work reliably on Chrome for the time being; see [this bug](https://github.com/whatwg/fetch/issues/722).
+
+## Running the Tests
+
+First, start the server-side:
+
+> node server.js
+
+Then, configure your CDN to use port `8000` on that hostname as the origin. Point a browser (as above, currently Chrome) to the CDN.
+
+
+
+## Test Format
+
+Each test run gets its own URL, randomized content, and operates independently.
+
+Tests are kept in JavaScript files in `tests/`, each file representing a suite.
+
+A suite is an object with a `name` member and a `tests` member; e.g.,
+
+```javascript
+export default {
+  name: 'Example Tests',
+  tests: [ ... ]
+}
+```
+
+The `tests` member is an array of objects, with the following members:
+
+- `name` - The name of the test.
+- `requests` - a list of request objects (see below).
+- `browser_only` - if `true`, will not run on non-browser caches.
+- `browser_skip` - if `true, will not run on browser caches.
+
+Possible members of a request object:
+
+- `template` - A template object for the request, by name -- see `templates.js`.
+- `request_method` - A string containing the HTTP method to be used.
+- `request_headers` - An array of `[header_name_string, header_value_string]` arrays to
+                    emit in the request.
+- `request_body` - A string to use as the request body.
+- `query_arg` - query arguments to add.
+- `filename` - filename to use.
+- `mode` - The mode string to pass to `fetch()`.
+- `credentials` - The credentials string to pass to `fetch()`.
+- `cache` - The cache string to pass to `fetch()`.
+- `pause_after` - Boolean controlling a 3-second pause after the request completes.
+- `response_status` - A `[number, string]` array containing the HTTP status code
+                    and phrase to return.
+- `response_headers` - An array of `[header_name_string, header_value_string]` arrays to
+                     emit in the response. These values will also be checked like
+                     expected_response_headers, unless there is a third value that is
+                     `false`.
+- `response_body` - String to send as the response body. If not set, it will contain
+                  the test identifier.
+- `expected_type` - One of `["cached", "not_cached", "lm_validate", "etag_validate", "error"]`
+- `expected_status` - A number representing a HTTP status code to check the response for.
+                    If not set, the value of `response_status[0]` will be used; if that
+                    is not set, 200 will be used.
+- `expected_request_headers` - An array of `[header_name_string, header_value_string]` representing
+                              headers to check the request for.
+- `expected_response_headers` - An array of `[header_name_string, header_value_string]` representing
+                              headers to check the response for. See also response_headers.
+- `expected_response_text` - A string to check the response body against.
+
+`server.js` stashes an entry containing observed headers for each request it receives. When the
+test fetches have run, this state is retrieved and the expected_* lists are checked, including
+their length.
+