tree: 5e3c9708e07ce04164d85b0ed648e56a89a2bc3d [path history] [tgz]
  1. op1 cspfp-comma-in-policy.json
  2. op10 cspfp-valid.json
  3. op100 manifest-mimetype.json
  4. op11 no-ids.json
  5. op12 empty-ids.json
  6. op13 empty-ids-after-nonempty.json
  7. op14 non-array-id.json
  8. op15 mix-of-ids.json
  9. op16 two-ids.json
  10. op2 cspfp-double-top-level.json
  11. op3 cspfp-double-second-level.json
  12. op4 csp-non-array.json
  13. op5 cspfp-non-object.json
  14. op6 cspfp-non-string.json
  15. op7 csp-noimg-report-only.json
  16. op8 csp-noimg.json
  17. op9 csp-valid-with-multi-item-array.json
  18. op97 utf-8-with-bom.json
  19. op98 utf-16le.json
  20. op99 csp-valid-manifest-with-404.json
  21. README.md
chromium/src/third_party/blink/web_tests/external/wpt/origin-policy/policies/README.md

These policies are served via the Python script at /.well-known/origin-policy. Their filenames must be in the form subdomain human-facing-string-with-no-spaces.json. They will be served in response to requests to that subdomain.

The human-facing string has no impact on the tests, and just makes it easier to scroll through the list.

The list of potential hostnames is created by tools/serve/serve.py's _make_origin_policy_subdomains function, and can be expanded as necessary.

At the moment, the origin policies starting at 100 downward have special handling in the /.well-known/origin-policy handler, and might require consulting that file to get the full context. The ones starting at 1 upward are handled generically. If they ever start meeting in the middle we can reevaluate this scheme.