HowToReportABug - Lighttpd - lighty labs
How to report a bug¶ The lighttpd issue tracker is for issues in lighttpd, not for user questions. Please direct questions to the Forums If you find a bug in lighttpd you can help a lot to find a fix for it by following some simple steps: Don't Panic For support questions (How do I... ?), please use the Forums! If you are new to lighttpd or have a question, then there is most likely not an issue i
HowToWriteALighttpdPlugin - Lighttpd - lighty labs
Writing Plugins¶ Before you start writing your own plugin, you should be able to build lighttpd (lighttpd source code and build instructions) and should feel comfortable with the basic data types and main headers in lighttpd: buffer (buffer.h) array (array.h) chunk (chunk.h) request (request.h) global structures (base.h) Next read the server internals: The State Engine of lighttpd Plugin Interface
delay request handling for stupid crawlers - lighty's life
I’m sure you know what “Crawl-Delay” is, but you may or may not know that, not all search engine crawlers support this nice stuff. What to do for those don’t obey the instrustion? They’ll eat all your Mbits/month or slow your webserver down. OK, ban it with url.access-deny. This is the only option u can choose before. But you don’t want to remove your pages from the stupid search engine index, do
lighttpdでモジュールを書く際に気をつけること - グニャラくんのグニャグニャ備忘録@はてな
LighttpdUnderSupervise - Lighttpd - lighty labs
Running Lighttpd under daemontools/supervise¶ Lighttpd is well suited to run monitored by the "supervise" program from Daniel J. Bernstein's daemontools package. To set it up, you must first create a standard service directory structure. In the following example the service directory from where the process starts will be /srv/lighttpd-main/. It consists of the following directory and files: /srv/l
Persistence is Power:lighttpdで指定のリクエストヘッダ項目を参照するプラグインを書いた - livedoor Blog（ブログ）
Days in programming, computing, studying, considering and enjoying lighttpd-1.4.15 + FastCGI な環境で、HTTP リクエストヘッダ中の任意のレコードを参照して、その内容によって環境変数を設定しておきたい、という状況。apache であれば SetEnvIf ディレクティブを使うことで、 SetEnvIf X-Hoge ".*" bar=yes とかで設定できるが、lighttpdではこういう事ができないらしい。lighttpdの設定でSetEnvIfのような条件分岐処理を書こうとすると、マニュアルのConditional Configurationによれば、 <field> <operator> <value> { ... } てな記述ができるのだが、<field> に指定できるのは
Apache 2.2 experimental/event MPM に降参 - Backnumbers: Steps to Phantasien
前回のつづき. そもそも Apache のコードを読んだのは, Comet みたいにちびちびはりっぱな HTTP ハンドラを C++ で書ける基盤はないかというもっと壮大な現実逃避の一部なのだった. (逃避は壮大なほどいい. 現実味が乏しくなるから...) 速いという評判から, 最初は lighttpd のコードを眺めていた. でも lighttpd のコードはやや男らしすぎる. この上で作業をするのは辛そうだ. それに中の人が同じ路線で mod_mailbox を作る と言っている. こっちを待つ方が良い気もする. (今のところ進展はなさそう.) Apache は I/O の多重化をしていないという話が "Apache の話" に 書いてあるのを読みしょんぼりしていたが, 一方で Apache 2.2 から入った event MPM のマニュアル には "keep alive probl
Welcome to REFWELL.COM
Well Interaction Analysis, Decision Support, Prod. Monitoring
Lighttpd+Pound with Catalyst or Mongrel
Not everyone chooses to go the FCGI way of deploying their web applications. Some people, like I, prefer deploying applications under Catalyst's httpd or Rails' Mongrel. Unfortunately, Lighttpd at this time (version 1.4.13) has a inept mod_proxy module. It does not load balance correctly and nor does it recover from a downed proxy node, requiring a full restart. Obviously this is unacceptable when
Docs ModProxyCore - Lighttpd - lighty labs
Installation¶ mod-proxy-core requires lighttpd 1.5 and is intended to replace mod_fastcgi. If you want to use mod-proxy-core you have to load it first. Each protocol is a module too and has to be loaded after the core-module.: server.modules = ( ..., "mod_proxy_core", "mod_proxy_backend_http", "mod_proxy_backend_fastcgi", ... ) Load Balancing¶ mod-proxy-core supports 4 different load balancers: th
Faster Web 2.0 - lighty's life
In Faster FastCGI I talked about using temp-files in /dev/shm to reduce the overhead of large FastCGI requests. Robert implemented it right away and it is available in the latest pre-release Woken up far too early and having the first coffee I shared some ideas on how this could be useful to accelerate AJAX based applications. Large Response content Robert already did some benchmarking and it look
Lighttpd prevent image hotlinking or leeching or direct linking - nixCraft
Save and close the file. Restart lighttpd webserver: # /etc/init.d/lighttpd restart Final configuration includes support for MSN, Google, Yahoo cache 🙂 $HTTP["referer"] !~ "^($|http://.*\.(google\.*|yahoo\.*|msn\.*|cyberciti\.biz|msnscache\.com/.*))" { $HTTP["referer"] !~ "^($|http://theos\.in|^$|nixcraft\.com|cricketnow\.in)" { $HTTP["useragent"] !~ "msnbot-media" { $HTTP["useragent"] !~ "Mediap
lighttpd vs Perlbal : blog.nomadscafe.jp
lighttpd vs Perlbal lighttpdのlinux-aioサポートの記事を読んでいて気になったので、既にaioをサポートしているPerlbalの静的コンテンツを配信するWebサーバとしての性能を調べてみた。 サーバは CPU Pen4 2.8GHz ( HyperThreading付き) Memory 512MB FedoraCore6 な環境です。 上記の記事の様にファイルを3GBほど作成（メモリーより明らかに多い量） 小さい画像ファイルと見立てて、3KBのファイルを10*100*1000=1M個作成しました。 #/bin/bash for i in `seq 1 10`; do for k in `seq 1 100`; do mkdir -p $i/$k; for j in `seq 1 1000`; do dd if=/dev/zero of=$i/$k/$j b
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
lighttpd 1.4.22 released - lighty's life
1.4.21 - "Yes we can... do another release" - Lighttpd - fly light
PRE-RELEASE: 1.4.21-r2392 - lighty's life
http://www.lighttpd.net/2008/9/30/1-4-20-Otherwise-the-terrorists-win
PRE-RELEASE: lighttpd-1.5.0-r1857.tar.gz - lighty's life
lighttpd.net runs on 1.5.0 - lighty's life
Announce: official lighttpd support