Feature #2212
closedAllow specifying a header parameter for mod_flv_streaming
Description
If serving flv files containing H.264 with mod_flv_streaming, the H.264 parameters are stored in a separate packet at the start of the file. Without these parameters, the rest of the file is undecodeable. Due to this, such a file served through mod_flv_streaming will not be decodeable, unless the receiver already has decoded the start of the file normally.
If the client knows about this, he could request to get this data included in the header prepended to the actual requested data. This is implemented by the attached patch.
If no header= parameter is included in the request, it includes the first 13 bytes of the file as a header, which should be mostly equal to the hardcoded FLV header that mod_flv_streaming currently includes. If a header= parameter is included, on the other hand, it includes that many bytes as a header, which then could include the H.264 header/parameter packet.
Files
Updated by mstorsjo almost 14 years ago
In practice, the headers packets can be located a bit into the stream, so including a consecutive segment from the start of the file may not always be the best solution. Something like the HTTP range header with multiple ranges would be a better solution - but returning all data in one stream instead of separate mime chunks, and specifying the ranges using query parameters instead of http headers. I ended up implementing something like that using mod_magnet and lua instead, so this patch can be skipped for now.
Updated by gstrauss about 8 years ago
- Status changed from Patch Pending to Wontfix
Thanks for sharing. Declining, per user note. Might reconsider if supported by more streaming clients.
Updated by gstrauss 4 months ago
- Status changed from Wontfix to Obsolete
- ASK QUESTIONS IN Forums set to No
mod_flv_streaming is no longer part of the lighttpd base
For replacement, see lua mod_flv_streaming
Also available in: Atom