traffic-advice.json (private prefetch proxy opt-in)
A traffic-advice document opting a fictional origin into private prefetch proxy traffic at full fraction while disallowing every other agent. For testing prefetch-proxy discovery and the JSON-array (not object) top level this format uses.
[
{
"user_agent": "prefetch-proxy",
"disallow": false,
"fraction": 1.0
},
{
"user_agent": "*",
"disallow": true
}
]
Specifications
- Seed
- 70400
- Site
- example.com (fictional)
- Format
- traffic-advice
- Rules
- 2
- Fraction
- 1
- Location
- /.well-known/traffic-advice
Testing contract
Expected to pass- Scenario
- Ask whether a private prefetch proxy may prefetch from this origin.
- Expected result
- The array is read top-level, the prefetch-proxy rule matches first and returns disallow=false with fraction 1.0, and every other user agent falls through to the wildcard rule and is refused.
What is a .json file?
JSON (JavaScript Object Notation) is a lightweight, text-based data-interchange format representing objects, arrays, strings, numbers, booleans, and null. It is language-independent, human-readable, and the dominant format for web APIs and configuration. It requires a single well-formed root value.
How to use this file
Use an example JSON file to test parsers and serializers, schema validation, Unicode and number-precision handling, and API request or response processing.
How to use this file for testing
“traffic-advice.json (private prefetch proxy opt-in)” is a deterministic Novus Examples fixture for Web assets, JSON parsing, Performance testing. Favicons, web app manifests, service workers, robots and sitemap files, Open Graph images, and .well-known resources — for testing web tooling, crawlers, PWA installers, and asset pipelines.
Documented properties for this file: seed 70400 · traffic-advice. Compare results against paired or grouped companions on this page when present (clean↔damaged, searchable↔scanned, or format twins) so scores stay reproducible across runs.
Download the file once, keep the path stable in CI or local scripts, and treat the spec table as the contract: dimensions, seeds, field lists, and roles are intentional. Corrupt or invalid samples are labelled as such — expect parsers to fail loudly rather than silently accept them.
Web-platform fixtures are standards-compliant samples against fictional example.com data. Test crawlers, PWA installers and manifest validators, favicon/icon pipelines, service-worker registration, or .well-known parsers against the documented structure.
Code examples
import json
with open("traffic-advice.json") as f:
data = json.load(f)
print(type(data), len(data))Related files
- jsonapple-app-site-associationAn Apple app-site-association file declaring Universal Links, web credentials, and app clips — normally served without an extension at /.well-known/, for testing AASA parsers (shown here as .json).
- jsonassetlinks.json (Android)An Android Digital Asset Links file granting app-link handling to a package via a certificate fingerprint (sample) — for testing assetlinks.json parsers and App Links verification.
- jsonWell-Known — Assetlinks Extra.well-known SAMPLE JSON (assetlinks-extra) for crawler and client discovery tests.
- jsonWell-Known — Change Password Rel.well-known SAMPLE JSON (change-password-rel) for crawler and client discovery tests.
- jsonWell-Known — Gpc Policy.well-known SAMPLE JSON (gpc-policy) for crawler and client discovery tests.
- jsonWell-Known — Nodeinfo Stub.well-known SAMPLE JSON (nodeinfo-stub) for crawler and client discovery tests.
Generated by generation/web_p7.py. Free for any use, no attribution required — license.