Code format
Fichiers d'echantillon HTTP
HTTP (.http) files store raw request definitions used by REST clients and API replay tools. Use sample HTTP files to test request templating, replay workflows, webhook debugging, and contract validation.
4 fichiers
All to 50KB
SHA256 verified
Manifeste included
Quick facts
Files first
HTTP Sample Files — Download
Starter file
TelechargerAPI Replay HTTP
Telecharger le fixtureWebhook Signature HTTP
Telecharger le fixture| Nom du fichier | Taille | MIME | Telecharger |
|---|---|---|---|
| 271 B | application/octet-stream |
Telecharger
|
|
| 271 B | application/octet-stream |
Telecharger
|
|
| 572 B | application/octet-stream |
Telecharger
|
|
| 295 B | application/octet-stream |
Telecharger
|
No files match the current filter. Switch to another chip or size range.
Use cases
HTTP Testing Workflows
Use the file table first, then branch into compare or FAQ only if the task needs more context.
Compare and decide
HTTP Format Comparisons
FAQ and reference
HTTP File FAQ
Verification du checksum
Utilisez les checksums pour confirmer l'integrite du fichier apres telechargement.
shasum -a 256 your_file_name_here
# Compare output with SHA256 values listed above.Where is the machine-readable manifest?
Use the manifest when you need stable names, SHA256 values, and URLs for automation.
Use in code — curl, Python, Node, wget
Copy any snippet directly into scripts, test suites, or CI pipelines. All URLs are stable and publicly accessible with no auth required.
# Download http_api_replay_request_sample.http
curl -L -o http_api_replay_request_sample.http \
https://samplefile.com/samples/download/code/http/http_api_replay_request_sample.http/
# Or fetch a random HTTP file
curl -s "https://samplefile.com/samples/api/random?format=http" | jq -r '.download_url'# Download http_api_replay_request_sample.http
wget -O http_api_replay_request_sample.http \
https://samplefile.com/samples/download/code/http/http_api_replay_request_sample.http/import requests
# Download a specific file
url = "https://samplefile.com/samples/download/code/http/http_api_replay_request_sample.http/"
resp = requests.get(url)
with open("http_api_replay_request_sample.http", "wb") as f:
f.write(resp.content)
# Or fetch a random HTTP file via API
meta = requests.get("https://samplefile.com/samples/api/random?format=http").json()
resp = requests.get(meta["download_url"])
with open(meta["name"], "wb") as f:
f.write(resp.content)// Download a specific file
const fs = require("fs");
const https = require("https");
const url = "https://samplefile.com/samples/download/code/http/http_api_replay_request_sample.http/";
https.get(url, (res) => {
res.pipe(fs.createWriteStream("http_api_replay_request_sample.http"));
});
// Or fetch a random HTTP via the API
const meta = await fetch("https://samplefile.com/samples/api/random?format=http").then(r => r.json());
const file = await fetch(meta.download_url);
// use file.arrayBuffer(), file.body, etc.# Random HTTP file (JSON response)
GET https://samplefile.com/samples/api/random?format=http
# All HTTP files
GET https://samplefile.com/samples/api/files?format=http
# Manifest with SHA256 checksums
GET https://samplefile.com/samples/code/http/manifest.json
# Response includes: name, size_bytes, mime_type, sha256, download_urlMethodologie de validation
- Validate syntax-highlight pipelines and file-type detection.
- Test parser robustness for larger source samples.
- Confirm linting/formatting tools handle encoding correctly.
Matrice de fixtures
Utilisez la matrice HTTP pour choisir les bons fixtures propres, limites et casses pour ce format.
Ouvrir la matrice
Packs de workflow