Bug #1088
closedmod_flv_streaming on lighttpd 1.4.13 does not work in osx
Description
Using lighttpd 1.4.13 compiled with the exact same flags on osx (10.4.9) as on Red Hat Enterprise Linux ES release 4 (Nahant Update 4) ,
flv's stream properly from the linux box, but from the osx server all start at byte 0 regardless of start= parameter.
Both have identical lighttpd.conf file including module mod_flv_streaming and with flv-streaming.extensions = (".flv")
Updated by Anonymous about 18 years ago
Sorry, forgot to include my contact info. If you need any more info or proof of bug, I can be reached at james AT cyberflowsolutions.com
-- james
Updated by Anonymous about 18 years ago
Please accept my humble appology. Lightty works PERFECTLY and my flash team hates me.
Thank you.
-- James
-- james
Updated by Anonymous about 18 years ago
ok, last time I promise.
Apparently, accessing them directly, works fine.
However, accessing them through mod_sec_dl does not.
for testing purposes I have my docroot and my secdownload.document-root set the same.
eg:
will show the exact same content from the exact same start point as:
http://pod1.dev/sec/50a66acc27fa0b497fa18bf7b4ae321d/46031e6f/video/5/25/28/152/high.flv?start=0
but,
http://pod1.dev/video/5/25/28/152/high.flv?start=25580015
will actually start at the keyframe 25580015 bytes in, as opposed to
http://pod1.dev/video/5/25/28/152/high.flv?start=0
which starts at the beginning.
I have the same server configuration on RHEL 4.0 and it works fine.
Any advice greatly appreciated.
Thank you.
-- James
-- james
Updated by jbarros almost 18 years ago
please mark this ticket as solved. placing mod_secdownload before mod_flvstreaming in lighttpd.conf solves this. I could have SWORN I tried that, but apparently I didnt.
-- James
Updated by stbuehler about 17 years ago
- Status changed from New to Fixed
- Resolution set to invalid
Also available in: Atom