Lighttpd for playing mp4 video

Jungle Boogie <jungleboogie0 <at> gmail.com>
2015-01-12 19:54:13 GMT

Hello All,
I'm running FreeBSD 10.1-Release with Lighttpd from pkg version 1.4.35_5
compiled as shown here: https://www.freshports.org/www/lighttpd/
Is it possible with my current configuration to have mp4 files played in a
browser and NOT downloaded?
I have added a line in /usr/local/etc/lighttpd/conf.d/mime.conf to read like this:
61: ".mp4" => "video/quicktime",
So now in the browser is displays the type correctly but it still wants to
download.
I don't need linking to a specific timecode, just start and stop.
Is there something additional that need installing to complete this?
Thanks,
jungle
--
--
inum: 883510009027723
sip: jungleboogie <at> sip2sip.info
xmpp: jungle-boogie <at> jit.si

phsysical.basedir vs. physical.doc_root

Edgar Fuß <ef <at> math.uni-bonn.de>
2014-02-14 18:08:39 GMT

I have a Lua script that modifies lighty.env["physical.doc-root"], yet, in the FastCGI handler, the
value of the DOCUMENT_ROOT environment variable doesn't reflect that change.
I found out that, in mod_fastcgi (and mod_cgi and mod_scgi), DOCUMENT_ROOT is set from physical.basedir,
while in mod_ssi, it's set from physical.coc_root.
So, what's the difference supposed to be between physical.doc_root and physical.basedir? The choice of
which of both to pick looks erratic to me, but that's probably due to my lack of understanding.
In response.c, both are set to the same value, but from there on, their use disgresses in a way not obvious to
me. mod_alias modifies basedir in a way I don't understand (it looks erroneous to me); mod_simple_vhost,
mod_indexfile and others operate on doc_root as I would expect.
Can someone please enlighten me?

Code Coverage Mode

Hi,
Is there any way to make Lighttpd run in "Code Coverage Mode" for PHP?
What I'm trying to achieve is a way to run, e.g., XDebug's Code
Coverage functionality in a non-intrusive way (without modifying the
PHP code to include code coverage statements) once the server starts
and have a log of all lines and counts once the server shuts down (and
while the server is running, with a refresh interval).
I've read around and it looks like WebSphere + Rational Application
Developer provides such functionality, is there anything similar for
Lighttpd?
Thanks in advance.
David E. Narváez

Lighttpd plugins and debian packaging

Anthony L. Awtrey <tony <at> awtrey.com>
2012-08-03 17:39:19 GMT

Hello,
Short version:
Can someone more-or-less officially provide guidance to distro
maintainers on how to build lighttpd plugins outside of the source tree?
Longer version:
I am migrating from Apache to Lighttpd and want to port some of the
custom plugins I've written. I found the official way to develop
plugins for lighttpd is by working in the source tree, copying the
mod_skeleton.c and hacking up the build to compile it together with
the lighttpd daemon.
http://redmine.lighttpd.net/projects/lighttpd/wiki/HowToWriteALighttpdPlugin
This has some obvious drawbacks from my point of view. I run Debian
and if I maintain a custom lighttpd package version with my plugins,
then I have to update my lighttpd package manually every time a new
lighttpd release comes out that fixes bugs or provides security fixes.
The Debian maintainers don't want to provide a lighttpd-dev package
because they are convinced it deviates too much from upstream. When I
asked about it, I was told that:
"well, upstream would need to provide a set of headers, libraries and
tools which are explicitly meant to develop. This isn't the case for
Lighttpd. We only could pick some random headers and maybe the skeleton
example and package it as -dev packages. These may, or may not be stable
APIs and headers - we can't know."
Full thread here:
http://lists.alioth.debian.org/pipermail/pkg-lighttpd-maintainers/2012-August/004023.html
Based upon this other, 6 year-old lighttpd thread it appears to be
relatively straight-forward to build and maintain plugins outside the
tree:
http://thread.gmane.org/gmane.comp.web.lighttpd/3507
Another point is that Ubuntu seems to deviate from Debian's lighttpd
package and *does* provide a lighttpd-dev package for this purpose, so
it appears to be at least possible.
Can someone more-or-less officially provide guidance to distro
maintainers on how to build plugins outside of the source tree?
Thanks in advance! Looking forward to using lighttpd more often in
production once I can get issue this resolved.
Tony

ssl.ciphers vs. ssl.cipher-list

Christian Kujau <lists <at> nerdbynature.de>
2011-12-15 11:12:53 GMT

Hi,
the config example added in r2814 (for the lighttpd-1.4.x branch)
mentioned that "ssl.ciphers" could be used to specify allowed ciphers. But
when configured, error.log says:
2011-12-15 10:03:32: (server.c.968) WARNING: unknown config-key:
ssl.ciphers (ignored)
The documented[0] "ssl.cipher-list" works though. Is "ssl.ciphers" the
new "ssl.cipher-list", even in lighttpd-1.4 and soon to be supported? Or
is the config example wrong?
Thanks,
Christian.
[0] http://redmine.lighttpd.net/wiki/1/Docs:SSL--
--
BOFH excuse #317:
Internet exceeded Luser level, please wait until a luser logs off before attempting to log back on.