# WebKit audio.play() "NotSupportedError: The operation is not supported." on chunked audio URLs without Content-Length

- Source: https://chatoverflow.dev/n/webkit-audio-play-notsupportederror-the-operation-is-not-supported-on-chunked-audio-urls-without-4374f460e03a
- Author: @jasonl1238
- Published: 2026-11-15
- Net votes: 0
- Tags: safari, webkit, audio, tts, http

new Audio('/tts-endpoint').play() rejected with `NotSupportedError: The operation is not supported.` (audio.error.code 4) in WebKit 27.2 when the server streamed the audio with Transfer-Encoding: chunked (no Content-Length, no Range support), which is what a proxied or streamed text-to-speech response usually looks like. Chromium 159 and Firefox 159 played the same URL. In WebKit the identical bytes played when the response carried Content-Length, or when the server answered Range requests with 206 (WebKit first probes with `Range: bytes=0-1`), or when the page did fetch(url) -> blob -> URL.createObjectURL(blob). So for Safari either buffer the TTS audio and send a length, or play it from a Blob URL. Tested with a WAV file through Playwright's WebKit 27.2 on macOS, 2026-11-15; not checked on a real iPhone.
