HTTP Content-Disposition, Byte-Range 206 Streaming, CORS and Cache-Control Across 54 Formats: Questions and Answers

Engineering reference answering 100 distinct technical questions on configuring HTTP response headers, RFC 6266 filenames, HTTP 206 Partial Content byte ranges, CORS preflights, and CDN caching rules across all 54 formats across all 54 file formats supported by SampleTestFiles.

Representative format hubs and diagnostic tools

Part 1: Document, spreadsheet and text format questions

1. Which exact HTTP response headers should accompany a .avro (Avro) download to ensure safe browser handling and accurate caching?
Send Content-Type: application/avro, Content-Length: 1024, Content-Disposition: attachment; filename="sample-avro-1kb.avro", X-Content-Type-Options: nosniff, and Accept-Ranges: bytes so HTTP caches and Data clients handle .avro predictably.
2. Which exact HTTP response headers should accompany a .bin (BIN) download to ensure safe browser handling and accurate caching?
Send Content-Type: application/octet-stream, Content-Length: 1024, Content-Disposition: attachment; filename="sample-bin-1kb.bin", X-Content-Type-Options: nosniff, and Accept-Ranges: bytes so HTTP caches and Testing clients handle .bin predictably.
3. Which exact HTTP response headers should accompany a .bmp (BMP) download to ensure safe browser handling and accurate caching?
Send Content-Type: image/bmp, Content-Length: 10240, Content-Disposition: attachment; filename="sample-bmp-10kb.bmp", X-Content-Type-Options: nosniff, and Accept-Ranges: bytes so HTTP caches and Images clients handle .bmp predictably.
4. Which exact HTTP response headers should accompany a .css (CSS) download to ensure safe browser handling and accurate caching?
Send Content-Type: text/css, Content-Length: 1024, Content-Disposition: attachment; filename="sample-css-1kb.css", X-Content-Type-Options: nosniff, and Accept-Ranges: bytes so HTTP caches and Code clients handle .css predictably.
5. Which exact HTTP response headers should accompany a .csv (CSV) download to ensure safe browser handling and accurate caching?
Send Content-Type: text/csv, Content-Length: 1024, Content-Disposition: attachment; filename="sample-csv-1kb.csv", X-Content-Type-Options: nosniff, and Accept-Ranges: bytes so HTTP caches and Spreadsheets clients handle .csv predictably.
6. Which exact HTTP response headers should accompany a .docx (DOCX) download to ensure safe browser handling and accurate caching?
Send Content-Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document, Content-Length: 51200, Content-Disposition: attachment; filename="sample-docx-50kb.docx", X-Content-Type-Options: nosniff, and Accept-Ranges: bytes so HTTP caches and Documents clients handle .docx predictably.
7. Which exact HTTP response headers should accompany a .eml (EML) download to ensure safe browser handling and accurate caching?
Send Content-Type: message/rfc822, Content-Length: 1024, Content-Disposition: attachment; filename="sample-eml-1kb.eml", X-Content-Type-Options: nosniff, and Accept-Ranges: bytes so HTTP caches and Email & Calendar clients handle .eml predictably.
8. Which exact HTTP response headers should accompany a .epub (EPUB) download to ensure safe browser handling and accurate caching?
Send Content-Type: application/epub+zip, Content-Length: 10240, Content-Disposition: attachment; filename="sample-epub-10kb.epub", X-Content-Type-Options: nosniff, and Accept-Ranges: bytes so HTTP caches and Ebooks clients handle .epub predictably.
9. Which exact HTTP response headers should accompany a .flac (FLAC) download to ensure safe browser handling and accurate caching?
Send Content-Type: audio/flac, Content-Length: 102400, Content-Disposition: attachment; filename="sample-flac-100kb.flac", X-Content-Type-Options: nosniff, and Accept-Ranges: bytes so HTTP caches and Audio clients handle .flac predictably.
10. Which exact HTTP response headers should accompany a .geojson (GeoJSON) download to ensure safe browser handling and accurate caching?
Send Content-Type: application/geo+json, Content-Length: 1024, Content-Disposition: attachment; filename="sample-geojson-1kb.geojson", X-Content-Type-Options: nosniff, and Accept-Ranges: bytes so HTTP caches and GIS clients handle .geojson predictably.
11. Which exact HTTP response headers should accompany a .gif (GIF) download to ensure safe browser handling and accurate caching?
Send Content-Type: image/gif, Content-Length: 10240, Content-Disposition: attachment; filename="sample-gif-10kb.gif", X-Content-Type-Options: nosniff, and Accept-Ranges: bytes so HTTP caches and Images clients handle .gif predictably.
12. Which exact HTTP response headers should accompany a .gltf (glTF) download to ensure safe browser handling and accurate caching?
Send Content-Type: model/gltf+json, Content-Length: 1024, Content-Disposition: attachment; filename="sample-gltf-1kb.gltf", X-Content-Type-Options: nosniff, and Accept-Ranges: bytes so HTTP caches and 3D Models clients handle .gltf predictably.
13. Which exact HTTP response headers should accompany a .gpx (GPX) download to ensure safe browser handling and accurate caching?
Send Content-Type: application/gpx+xml, Content-Length: 1024, Content-Disposition: attachment; filename="sample-gpx-1kb.gpx", X-Content-Type-Options: nosniff, and Accept-Ranges: bytes so HTTP caches and GIS clients handle .gpx predictably.
14. Which exact HTTP response headers should accompany a .gz (GZ) download to ensure safe browser handling and accurate caching?
Send Content-Type: application/gzip, Content-Length: 1024, Content-Disposition: attachment; filename="sample-gz-1kb.gz", X-Content-Type-Options: nosniff, and Accept-Ranges: bytes so HTTP caches and Archives clients handle .gz predictably.
15. Which exact HTTP response headers should accompany a .html (HTML) download to ensure safe browser handling and accurate caching?
Send Content-Type: text/html, Content-Length: 1024, Content-Disposition: attachment; filename="sample-html-1kb.html", X-Content-Type-Options: nosniff, and Accept-Ranges: bytes so HTTP caches and Documents clients handle .html predictably.
16. Which exact HTTP response headers should accompany a .ico (ICO) download to ensure safe browser handling and accurate caching?
Send Content-Type: image/vnd.microsoft.icon, Content-Length: 10240, Content-Disposition: attachment; filename="sample-ico-10kb.ico", X-Content-Type-Options: nosniff, and Accept-Ranges: bytes so HTTP caches and Images clients handle .ico predictably.
17. Which exact HTTP response headers should accompany a .ics (iCalendar) download to ensure safe browser handling and accurate caching?
Send Content-Type: text/calendar, Content-Length: 1024, Content-Disposition: attachment; filename="sample-ics-1kb.ics", X-Content-Type-Options: nosniff, and Accept-Ranges: bytes so HTTP caches and Email & Calendar clients handle .ics predictably.
18. Which exact HTTP response headers should accompany a .ini (INI) download to ensure safe browser handling and accurate caching?
Send Content-Type: text/plain, Content-Length: 1024, Content-Disposition: attachment; filename="sample-ini-1kb.ini", X-Content-Type-Options: nosniff, and Accept-Ranges: bytes so HTTP caches and Configuration clients handle .ini predictably.
19. Which exact HTTP response headers should accompany a .jpg (JPG) download to ensure safe browser handling and accurate caching?
Send Content-Type: image/jpeg, Content-Length: 1024, Content-Disposition: attachment; filename="sample-jpg-1kb.jpg", X-Content-Type-Options: nosniff, and Accept-Ranges: bytes so HTTP caches and Images clients handle .jpg predictably.
20. Which exact HTTP response headers should accompany a .js (JavaScript) download to ensure safe browser handling and accurate caching?
Send Content-Type: text/javascript, per RFC 9239, Content-Length: 1024, Content-Disposition: attachment; filename="sample-js-1kb.js", X-Content-Type-Options: nosniff, and Accept-Ranges: bytes so HTTP caches and Code clients handle .js predictably.
21. Which exact HTTP response headers should accompany a .json (JSON) download to ensure safe browser handling and accurate caching?
Send Content-Type: application/json, Content-Length: 1024, Content-Disposition: attachment; filename="sample-json-1kb.json", X-Content-Type-Options: nosniff, and Accept-Ranges: bytes so HTTP caches and Data clients handle .json predictably.
22. Which exact HTTP response headers should accompany a .jsonl (JSONL) download to ensure safe browser handling and accurate caching?
Send Content-Type: application/jsonl, Content-Length: 1024, Content-Disposition: attachment; filename="sample-jsonl-1kb.jsonl", X-Content-Type-Options: nosniff, and Accept-Ranges: bytes so HTTP caches and Data clients handle .jsonl predictably.
23. Which exact HTTP response headers should accompany a .kml (KML) download to ensure safe browser handling and accurate caching?
Send Content-Type: application/vnd.google-earth.kml+xml, Content-Length: 1024, Content-Disposition: attachment; filename="sample-kml-1kb.kml", X-Content-Type-Options: nosniff, and Accept-Ranges: bytes so HTTP caches and GIS clients handle .kml predictably.
24. Which exact HTTP response headers should accompany a .log (LOG) download to ensure safe browser handling and accurate caching?
Send Content-Type: text/plain, Content-Length: 1024, Content-Disposition: attachment; filename="sample-log-1kb.log", X-Content-Type-Options: nosniff, and Accept-Ranges: bytes so HTTP caches and Testing clients handle .log predictably.
25. Which exact HTTP response headers should accompany a .m4a (M4A) download to ensure safe browser handling and accurate caching?
Send Content-Type: audio/mp4, Content-Length: 102400, Content-Disposition: attachment; filename="sample-m4a-100kb.m4a", X-Content-Type-Options: nosniff, and Accept-Ranges: bytes so HTTP caches and Audio clients handle .m4a predictably.

Part 2: Image, audio, video, archive and 3D format questions

1. Which exact HTTP response headers should accompany a .md (Markdown) download to ensure safe browser handling and accurate caching?
Send Content-Type: text/markdown, Content-Length: 1024, Content-Disposition: attachment; filename="sample-md-1kb.md", X-Content-Type-Options: nosniff, and Accept-Ranges: bytes so HTTP caches and Documents clients handle .md predictably.
2. Which exact HTTP response headers should accompany a .mkv (MKV) download to ensure safe browser handling and accurate caching?
Send Content-Type: video/x-matroska, Content-Length: 102400, Content-Disposition: attachment; filename="sample-mkv-100kb.mkv", X-Content-Type-Options: nosniff, and Accept-Ranges: bytes so HTTP caches and Video clients handle .mkv predictably.
3. Which exact HTTP response headers should accompany a .mov (MOV) download to ensure safe browser handling and accurate caching?
Send Content-Type: video/quicktime, Content-Length: 102400, Content-Disposition: attachment; filename="sample-mov-100kb.mov", X-Content-Type-Options: nosniff, and Accept-Ranges: bytes so HTTP caches and Video clients handle .mov predictably.
4. Which exact HTTP response headers should accompany a .mp3 (MP3) download to ensure safe browser handling and accurate caching?
Send Content-Type: audio/mpeg, Content-Length: 102400, Content-Disposition: attachment; filename="sample-mp3-100kb.mp3", X-Content-Type-Options: nosniff, and Accept-Ranges: bytes so HTTP caches and Audio clients handle .mp3 predictably.
5. Which exact HTTP response headers should accompany a .mp4 (MP4) download to ensure safe browser handling and accurate caching?
Send Content-Type: video/mp4, Content-Length: 102400, Content-Disposition: attachment; filename="sample-mp4-100kb.mp4", X-Content-Type-Options: nosniff, and Accept-Ranges: bytes so HTTP caches and Video clients handle .mp4 predictably.
6. Which exact HTTP response headers should accompany a .obj (OBJ) download to ensure safe browser handling and accurate caching?
Send Content-Type: model/obj, Content-Length: 1024, Content-Disposition: attachment; filename="sample-obj-1kb.obj", X-Content-Type-Options: nosniff, and Accept-Ranges: bytes so HTTP caches and 3D Models clients handle .obj predictably.
7. Which exact HTTP response headers should accompany a .ods (ODS) download to ensure safe browser handling and accurate caching?
Send Content-Type: application/vnd.oasis.opendocument.spreadsheet, Content-Length: 10240, Content-Disposition: attachment; filename="sample-ods-10kb.ods", X-Content-Type-Options: nosniff, and Accept-Ranges: bytes so HTTP caches and Spreadsheets clients handle .ods predictably.
8. Which exact HTTP response headers should accompany a .odt (ODT) download to ensure safe browser handling and accurate caching?
Send Content-Type: application/vnd.oasis.opendocument.text, Content-Length: 10240, Content-Disposition: attachment; filename="sample-odt-10kb.odt", X-Content-Type-Options: nosniff, and Accept-Ranges: bytes so HTTP caches and Documents clients handle .odt predictably.
9. Which exact HTTP response headers should accompany a .pdf (PDF) download to ensure safe browser handling and accurate caching?
Send Content-Type: application/pdf, Content-Length: 5120, Content-Disposition: attachment; filename="sample-pdf-5kb.pdf", X-Content-Type-Options: nosniff, and Accept-Ranges: bytes so HTTP caches and Documents clients handle .pdf predictably.
10. Which exact HTTP response headers should accompany a .png (PNG) download to ensure safe browser handling and accurate caching?
Send Content-Type: image/png, Content-Length: 1024, Content-Disposition: attachment; filename="sample-png-1kb.png", X-Content-Type-Options: nosniff, and Accept-Ranges: bytes so HTTP caches and Images clients handle .png predictably.
11. Which exact HTTP response headers should accompany a .pptx (PPTX) download to ensure safe browser handling and accurate caching?
Send Content-Type: application/vnd.openxmlformats-officedocument.presentationml.presentation, Content-Length: 102400, Content-Disposition: attachment; filename="sample-pptx-100kb.pptx", X-Content-Type-Options: nosniff, and Accept-Ranges: bytes so HTTP caches and Presentations clients handle .pptx predictably.
12. Which exact HTTP response headers should accompany a .rtf (RTF) download to ensure safe browser handling and accurate caching?
Send Content-Type: application/rtf, Content-Length: 1024, Content-Disposition: attachment; filename="sample-rtf-1kb.rtf", X-Content-Type-Options: nosniff, and Accept-Ranges: bytes so HTTP caches and Documents clients handle .rtf predictably.
13. Which exact HTTP response headers should accompany a .sql (SQL) download to ensure safe browser handling and accurate caching?
Send Content-Type: application/sql, Content-Length: 1024, Content-Disposition: attachment; filename="sample-sql-1kb.sql", X-Content-Type-Options: nosniff, and Accept-Ranges: bytes so HTTP caches and Database clients handle .sql predictably.
14. Which exact HTTP response headers should accompany a .srt (SRT) download to ensure safe browser handling and accurate caching?
Send Content-Type: application/x-subrip, Content-Length: 1024, Content-Disposition: attachment; filename="sample-srt-1kb.srt", X-Content-Type-Options: nosniff, and Accept-Ranges: bytes so HTTP caches and Subtitles clients handle .srt predictably.
15. Which exact HTTP response headers should accompany a .stl (STL) download to ensure safe browser handling and accurate caching?
Send Content-Type: model/stl, Content-Length: 1024, Content-Disposition: attachment; filename="sample-stl-1kb.stl", X-Content-Type-Options: nosniff, and Accept-Ranges: bytes so HTTP caches and 3D Models clients handle .stl predictably.
16. Which exact HTTP response headers should accompany a .svg (SVG) download to ensure safe browser handling and accurate caching?
Send Content-Type: image/svg+xml, Content-Length: 1024, Content-Disposition: attachment; filename="sample-svg-1kb.svg", X-Content-Type-Options: nosniff, and Accept-Ranges: bytes so HTTP caches and Images clients handle .svg predictably.
17. Which exact HTTP response headers should accompany a .tar (TAR) download to ensure safe browser handling and accurate caching?
Send Content-Type: application/x-tar, Content-Length: 10240, Content-Disposition: attachment; filename="sample-tar-10kb.tar", X-Content-Type-Options: nosniff, and Accept-Ranges: bytes so HTTP caches and Archives clients handle .tar predictably.
18. Which exact HTTP response headers should accompany a .tiff (TIFF) download to ensure safe browser handling and accurate caching?
Send Content-Type: image/tiff, Content-Length: 10240, Content-Disposition: attachment; filename="sample-tiff-10kb.tiff", X-Content-Type-Options: nosniff, and Accept-Ranges: bytes so HTTP caches and Images clients handle .tiff predictably.
19. Which exact HTTP response headers should accompany a .toml (TOML) download to ensure safe browser handling and accurate caching?
Send Content-Type: application/toml, Content-Length: 1024, Content-Disposition: attachment; filename="sample-toml-1kb.toml", X-Content-Type-Options: nosniff, and Accept-Ranges: bytes so HTTP caches and Configuration clients handle .toml predictably.
20. Which exact HTTP response headers should accompany a .tsv (TSV) download to ensure safe browser handling and accurate caching?
Send Content-Type: text/tab-separated-values, Content-Length: 1024, Content-Disposition: attachment; filename="sample-tsv-1kb.tsv", X-Content-Type-Options: nosniff, and Accept-Ranges: bytes so HTTP caches and Spreadsheets clients handle .tsv predictably.
21. Which exact HTTP response headers should accompany a .txt (TXT) download to ensure safe browser handling and accurate caching?
Send Content-Type: text/plain, Content-Length: 1024, Content-Disposition: attachment; filename="sample-txt-1kb.txt", X-Content-Type-Options: nosniff, and Accept-Ranges: bytes so HTTP caches and Documents clients handle .txt predictably.
22. Which exact HTTP response headers should accompany a .vtt (WebVTT) download to ensure safe browser handling and accurate caching?
Send Content-Type: text/vtt, Content-Length: 1024, Content-Disposition: attachment; filename="sample-vtt-1kb.vtt", X-Content-Type-Options: nosniff, and Accept-Ranges: bytes so HTTP caches and Subtitles clients handle .vtt predictably.
23. Which exact HTTP response headers should accompany a .wav (WAV) download to ensure safe browser handling and accurate caching?
Send Content-Type: audio/wav, Content-Length: 102400, Content-Disposition: attachment; filename="sample-wav-100kb.wav", X-Content-Type-Options: nosniff, and Accept-Ranges: bytes so HTTP caches and Audio clients handle .wav predictably.
24. Which exact HTTP response headers should accompany a .webm (WebM) download to ensure safe browser handling and accurate caching?
Send Content-Type: video/webm, Content-Length: 102400, Content-Disposition: attachment; filename="sample-webm-100kb.webm", X-Content-Type-Options: nosniff, and Accept-Ranges: bytes so HTTP caches and Video clients handle .webm predictably.
25. Which exact HTTP response headers should accompany a .webp (WebP) download to ensure safe browser handling and accurate caching?
Send Content-Type: image/webp, Content-Length: 10240, Content-Disposition: attachment; filename="sample-webp-10kb.webp", X-Content-Type-Options: nosniff, and Accept-Ranges: bytes so HTTP caches and Images clients handle .webp predictably.
26. Which exact HTTP response headers should accompany a .xlsx (XLSX) download to ensure safe browser handling and accurate caching?
Send Content-Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet, Content-Length: 10240, Content-Disposition: attachment; filename="sample-xlsx-10kb.xlsx", X-Content-Type-Options: nosniff, and Accept-Ranges: bytes so HTTP caches and Spreadsheets clients handle .xlsx predictably.
27. Which exact HTTP response headers should accompany a .xml (XML) download to ensure safe browser handling and accurate caching?
Send Content-Type: application/xml, Content-Length: 1024, Content-Disposition: attachment; filename="sample-xml-1kb.xml", X-Content-Type-Options: nosniff, and Accept-Ranges: bytes so HTTP caches and Data clients handle .xml predictably.
28. Which exact HTTP response headers should accompany a .yaml (YAML) download to ensure safe browser handling and accurate caching?
Send Content-Type: application/yaml, Content-Length: 1024, Content-Disposition: attachment; filename="sample-yaml-1kb.yaml", X-Content-Type-Options: nosniff, and Accept-Ranges: bytes so HTTP caches and Configuration clients handle .yaml predictably.
29. Which exact HTTP response headers should accompany a .zip (ZIP) download to ensure safe browser handling and accurate caching?
Send Content-Type: application/zip, Content-Length: 1024, Content-Disposition: attachment; filename="sample-zip-1kb.zip", X-Content-Type-Options: nosniff, and Accept-Ranges: bytes so HTTP caches and Archives clients handle .zip predictably.

Part 3: Architecture, implementation and pipeline questions

1. Why is Accept-Ranges: bytes important when serving a large .avro file over HTTP?
Supporting HTTP 206 Partial Content with Content-Range allows download managers to resume interrupted .avro transfers and enables media/archive readers to seek directly to specific offsets at byte offset 757.
2. Why is Accept-Ranges: bytes important when serving a large .bin file over HTTP?
Supporting HTTP 206 Partial Content with Content-Range allows download managers to resume interrupted .bin transfers and enables media/archive readers to seek directly to specific offsets at byte offset 1.
3. Why is Accept-Ranges: bytes important when serving a large .bmp file over HTTP?
Supporting HTTP 206 Partial Content with Content-Range allows download managers to resume interrupted .bmp transfers and enables media/archive readers to seek directly to specific offsets at byte offset 58.
4. Why is Accept-Ranges: bytes important when serving a large .css file over HTTP?
Supporting HTTP 206 Partial Content with Content-Range allows download managers to resume interrupted .css transfers and enables media/archive readers to seek directly to specific offsets at byte offset 220.
5. Why is Accept-Ranges: bytes important when serving a large .csv file over HTTP?
Supporting HTTP 206 Partial Content with Content-Range allows download managers to resume interrupted .csv transfers and enables media/archive readers to seek directly to specific offsets at byte offset 201.
6. Why is Accept-Ranges: bytes important when serving a large .docx file over HTTP?
Supporting HTTP 206 Partial Content with Content-Range allows download managers to resume interrupted .docx transfers and enables media/archive readers to seek directly to specific offsets at byte offset 37888.
7. Why is Accept-Ranges: bytes important when serving a large .eml file over HTTP?
Supporting HTTP 206 Partial Content with Content-Range allows download managers to resume interrupted .eml transfers and enables media/archive readers to seek directly to specific offsets at byte offset 420.
8. Why is Accept-Ranges: bytes important when serving a large .epub file over HTTP?
Supporting HTTP 206 Partial Content with Content-Range allows download managers to resume interrupted .epub transfers and enables media/archive readers to seek directly to specific offsets at byte offset 3072.
9. Why is Accept-Ranges: bytes important when serving a large .flac file over HTTP?
Supporting HTTP 206 Partial Content with Content-Range allows download managers to resume interrupted .flac transfers and enables media/archive readers to seek directly to specific offsets at byte offset 185.
10. Why is Accept-Ranges: bytes important when serving a large .geojson file over HTTP?
Supporting HTTP 206 Partial Content with Content-Range allows download managers to resume interrupted .geojson transfers and enables media/archive readers to seek directly to specific offsets at byte offset 120.
11. Why is Accept-Ranges: bytes important when serving a large .gif file over HTTP?
Supporting HTTP 206 Partial Content with Content-Range allows download managers to resume interrupted .gif transfers and enables media/archive readers to seek directly to specific offsets at byte offset 874.
12. Why is Accept-Ranges: bytes important when serving a large .gltf file over HTTP?
Supporting HTTP 206 Partial Content with Content-Range allows download managers to resume interrupted .gltf transfers and enables media/archive readers to seek directly to specific offsets at byte offset 1024.
13. Why is Accept-Ranges: bytes important when serving a large .gpx file over HTTP?
Supporting HTTP 206 Partial Content with Content-Range allows download managers to resume interrupted .gpx transfers and enables media/archive readers to seek directly to specific offsets at byte offset 700.
14. Why is Accept-Ranges: bytes important when serving a large .gz file over HTTP?
Supporting HTTP 206 Partial Content with Content-Range allows download managers to resume interrupted .gz transfers and enables media/archive readers to seek directly to specific offsets at byte offset 35.
15. Why is Accept-Ranges: bytes important when serving a large .html file over HTTP?
Supporting HTTP 206 Partial Content with Content-Range allows download managers to resume interrupted .html transfers and enables media/archive readers to seek directly to specific offsets at byte offset 700.
16. Why is Accept-Ranges: bytes important when serving a large .ico file over HTTP?
Supporting HTTP 206 Partial Content with Content-Range allows download managers to resume interrupted .ico transfers and enables media/archive readers to seek directly to specific offsets at byte offset 1024.
17. Why is Accept-Ranges: bytes important when serving a large .ics file over HTTP?
Supporting HTTP 206 Partial Content with Content-Range allows download managers to resume interrupted .ics transfers and enables media/archive readers to seek directly to specific offsets at byte offset 220.
18. Why is Accept-Ranges: bytes important when serving a large .ini file over HTTP?
Supporting HTTP 206 Partial Content with Content-Range allows download managers to resume interrupted .ini transfers and enables media/archive readers to seek directly to specific offsets at byte offset 120.
19. Why is Accept-Ranges: bytes important when serving a large .jpg file over HTTP?
Supporting HTTP 206 Partial Content with Content-Range allows download managers to resume interrupted .jpg transfers and enables media/archive readers to seek directly to specific offsets at byte offset 632.
20. Why is Accept-Ranges: bytes important when serving a large .js file over HTTP?
Supporting HTTP 206 Partial Content with Content-Range allows download managers to resume interrupted .js transfers and enables media/archive readers to seek directly to specific offsets at byte offset 700.
21. Why is Accept-Ranges: bytes important when serving a large .json file over HTTP?
Supporting HTTP 206 Partial Content with Content-Range allows download managers to resume interrupted .json transfers and enables media/archive readers to seek directly to specific offsets at byte offset 136.
22. Why is Accept-Ranges: bytes important when serving a large .jsonl file over HTTP?
Supporting HTTP 206 Partial Content with Content-Range allows download managers to resume interrupted .jsonl transfers and enables media/archive readers to seek directly to specific offsets at byte offset 37.
23. Why is Accept-Ranges: bytes important when serving a large .kml file over HTTP?
Supporting HTTP 206 Partial Content with Content-Range allows download managers to resume interrupted .kml transfers and enables media/archive readers to seek directly to specific offsets at byte offset 400.

Part 4: Verification, edge cases and automation questions

1. How do RFC 5987 / RFC 6266 filename* parameters protect non-ASCII .avro download filenames?
Providing both an ASCII fallback filename="sample.avro" and a UTF-8 percent-encoded filename*=UTF-8''sample.avro in Content-Disposition ensures every browser saves the .avro file with the right extension.
2. How do RFC 5987 / RFC 6266 filename* parameters protect non-ASCII .bin download filenames?
Providing both an ASCII fallback filename="sample.bin" and a UTF-8 percent-encoded filename*=UTF-8''sample.bin in Content-Disposition ensures every browser saves the .bin file with the right extension.
3. How do RFC 5987 / RFC 6266 filename* parameters protect non-ASCII .bmp download filenames?
Providing both an ASCII fallback filename="sample.bmp" and a UTF-8 percent-encoded filename*=UTF-8''sample.bmp in Content-Disposition ensures every browser saves the .bmp file with the right extension.
4. How do RFC 5987 / RFC 6266 filename* parameters protect non-ASCII .css download filenames?
Providing both an ASCII fallback filename="sample.css" and a UTF-8 percent-encoded filename*=UTF-8''sample.css in Content-Disposition ensures every browser saves the .css file with the right extension.
5. How do RFC 5987 / RFC 6266 filename* parameters protect non-ASCII .csv download filenames?
Providing both an ASCII fallback filename="sample.csv" and a UTF-8 percent-encoded filename*=UTF-8''sample.csv in Content-Disposition ensures every browser saves the .csv file with the right extension.
6. How do RFC 5987 / RFC 6266 filename* parameters protect non-ASCII .docx download filenames?
Providing both an ASCII fallback filename="sample.docx" and a UTF-8 percent-encoded filename*=UTF-8''sample.docx in Content-Disposition ensures every browser saves the .docx file with the right extension.
7. How do RFC 5987 / RFC 6266 filename* parameters protect non-ASCII .eml download filenames?
Providing both an ASCII fallback filename="sample.eml" and a UTF-8 percent-encoded filename*=UTF-8''sample.eml in Content-Disposition ensures every browser saves the .eml file with the right extension.
8. How do RFC 5987 / RFC 6266 filename* parameters protect non-ASCII .epub download filenames?
Providing both an ASCII fallback filename="sample.epub" and a UTF-8 percent-encoded filename*=UTF-8''sample.epub in Content-Disposition ensures every browser saves the .epub file with the right extension.
9. How do RFC 5987 / RFC 6266 filename* parameters protect non-ASCII .flac download filenames?
Providing both an ASCII fallback filename="sample.flac" and a UTF-8 percent-encoded filename*=UTF-8''sample.flac in Content-Disposition ensures every browser saves the .flac file with the right extension.
10. How do RFC 5987 / RFC 6266 filename* parameters protect non-ASCII .geojson download filenames?
Providing both an ASCII fallback filename="sample.geojson" and a UTF-8 percent-encoded filename*=UTF-8''sample.geojson in Content-Disposition ensures every browser saves the .geojson file with the right extension.
11. How do RFC 5987 / RFC 6266 filename* parameters protect non-ASCII .gif download filenames?
Providing both an ASCII fallback filename="sample.gif" and a UTF-8 percent-encoded filename*=UTF-8''sample.gif in Content-Disposition ensures every browser saves the .gif file with the right extension.
12. How do RFC 5987 / RFC 6266 filename* parameters protect non-ASCII .gltf download filenames?
Providing both an ASCII fallback filename="sample.gltf" and a UTF-8 percent-encoded filename*=UTF-8''sample.gltf in Content-Disposition ensures every browser saves the .gltf file with the right extension.
13. How do RFC 5987 / RFC 6266 filename* parameters protect non-ASCII .gpx download filenames?
Providing both an ASCII fallback filename="sample.gpx" and a UTF-8 percent-encoded filename*=UTF-8''sample.gpx in Content-Disposition ensures every browser saves the .gpx file with the right extension.
14. How do RFC 5987 / RFC 6266 filename* parameters protect non-ASCII .gz download filenames?
Providing both an ASCII fallback filename="sample.gz" and a UTF-8 percent-encoded filename*=UTF-8''sample.gz in Content-Disposition ensures every browser saves the .gz file with the right extension.
15. How do RFC 5987 / RFC 6266 filename* parameters protect non-ASCII .html download filenames?
Providing both an ASCII fallback filename="sample.html" and a UTF-8 percent-encoded filename*=UTF-8''sample.html in Content-Disposition ensures every browser saves the .html file with the right extension.
16. How do RFC 5987 / RFC 6266 filename* parameters protect non-ASCII .ico download filenames?
Providing both an ASCII fallback filename="sample.ico" and a UTF-8 percent-encoded filename*=UTF-8''sample.ico in Content-Disposition ensures every browser saves the .ico file with the right extension.
17. How do RFC 5987 / RFC 6266 filename* parameters protect non-ASCII .ics download filenames?
Providing both an ASCII fallback filename="sample.ics" and a UTF-8 percent-encoded filename*=UTF-8''sample.ics in Content-Disposition ensures every browser saves the .ics file with the right extension.
18. How do RFC 5987 / RFC 6266 filename* parameters protect non-ASCII .ini download filenames?
Providing both an ASCII fallback filename="sample.ini" and a UTF-8 percent-encoded filename*=UTF-8''sample.ini in Content-Disposition ensures every browser saves the .ini file with the right extension.
19. How do RFC 5987 / RFC 6266 filename* parameters protect non-ASCII .jpg download filenames?
Providing both an ASCII fallback filename="sample.jpg" and a UTF-8 percent-encoded filename*=UTF-8''sample.jpg in Content-Disposition ensures every browser saves the .jpg file with the right extension.
20. How do RFC 5987 / RFC 6266 filename* parameters protect non-ASCII .js download filenames?
Providing both an ASCII fallback filename="sample.js" and a UTF-8 percent-encoded filename*=UTF-8''sample.js in Content-Disposition ensures every browser saves the .js file with the right extension.
21. How do RFC 5987 / RFC 6266 filename* parameters protect non-ASCII .json download filenames?
Providing both an ASCII fallback filename="sample.json" and a UTF-8 percent-encoded filename*=UTF-8''sample.json in Content-Disposition ensures every browser saves the .json file with the right extension.
22. How do RFC 5987 / RFC 6266 filename* parameters protect non-ASCII .jsonl download filenames?
Providing both an ASCII fallback filename="sample.jsonl" and a UTF-8 percent-encoded filename*=UTF-8''sample.jsonl in Content-Disposition ensures every browser saves the .jsonl file with the right extension.
23. How do RFC 5987 / RFC 6266 filename* parameters protect non-ASCII .kml download filenames?
Providing both an ASCII fallback filename="sample.kml" and a UTF-8 percent-encoded filename*=UTF-8''sample.kml in Content-Disposition ensures every browser saves the .kml file with the right extension.

Explore all 40 topic-based technical format references

Browse the complete engineering reference library on Testing guides or Frequently asked questions.