<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://permalink.gmane.org/gmane.comp.web.lighttpd">
    <title>gmane.comp.web.lighttpd</title>
    <link>http://permalink.gmane.org/gmane.comp.web.lighttpd</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.lighttpd/5339"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.lighttpd/5337"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.lighttpd/5336"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.lighttpd/5335"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.lighttpd/5334"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.lighttpd/5333"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.lighttpd/5332"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.lighttpd/5331"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.lighttpd/5330"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.lighttpd/5329"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.lighttpd/5328"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.lighttpd/5327"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.lighttpd/5326"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.lighttpd/5325"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.lighttpd/5324"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.lighttpd/5323"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.lighttpd/5320"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.lighttpd/5316"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.lighttpd/5314"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.lighttpd/5313"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.lighttpd/5339">
    <title>(unknown)</title>
    <link>http://permalink.gmane.org/gmane.comp.web.lighttpd/5339</link>
    <description>&lt;pre&gt;


&lt;/pre&gt;</description>
    <dc:creator>James Marcus</dc:creator>
    <dc:date>2012-04-22T14:22:45</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.lighttpd/5337">
    <title>Re: lighttpd + php_cgi = 100% cpu usage</title>
    <link>http://permalink.gmane.org/gmane.comp.web.lighttpd/5337</link>
    <description>&lt;pre&gt;Hallo,

On 2012-03-12 22:56, Paulo Roberto Vieira Brandao wrote:
This really sounds like a problem in either PHP itself or the wiki software.
Processing PHP needs CPU time, of course, so *short* spikes in CPU usage
would be normal. What's not normal is the fact that you are actually
seeing these spikes (in "top" or something) and that the spikes seem to
last for a rather long time (&amp;gt;1s).
Assuming that one request to a wiki page consumes at least one PHP
process, probably even more (depending on the wiki software
architecture), it's not unlikely that 3 concurrent requests will consume
all available PHP ressources.

You might see an improvement when further increasing max-procs, but that
will not fix the source of your problem.

You could narrow it down by testing some other PHP-based software (even
if it only is some simple file including phpinfo()).

Other than that, you could try asking the suppliers of your wiki
software for support.


Best regards,

Christian


&lt;/pre&gt;</description>
    <dc:creator>Christian Hoffmann</dc:creator>
    <dc:date>2012-03-13T07:57:08</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.lighttpd/5336">
    <title>lighttpd + php_cgi = 100% cpu usage</title>
    <link>http://permalink.gmane.org/gmane.comp.web.lighttpd/5336</link>
    <description>&lt;pre&gt;Hi,

I just installed a lighttpd server with fast cgi running media wiki on an AWS EC2 Instance.
The wiki is running fine while only one person is connected, if 3 simultaneous access occurs it's impossible to use the Wiki.
2 instances of php_cgi consuming a total of 100% of cpu.
Using alone the application, each page access raises the cpu usage of the server to 35%.

I would like to know what could I do to have the server working properly.

Follow some information about my configuration:

Linux: 2.6.35.14-107.1.36.amzn1.i686

php_cgi:

php-cgi -v
PHP 5.3.10 (cgi-fcgi) (built: Feb  2 2012 23:45:39)
Copyright (c) 1997-2012 The PHP Group
Zend Engine v2.3.0, Copyright (c) 1998-2012 Zend Technologies

lighttpd:

ighttpd -v
lighttpd/1.4.29 (ssl) - a light and fast webserver
Build-Date: Jul 16 2011 04:55:02


lighttpd.conf


$SERVER["socket"] == ":80" {
        $HTTP["host"] =~ "example\.com\.br$" {
        url.redirect = ( "^/(.*)" =&amp;gt; "https://example.com.br/$1" )
    server.name                 = "example.com.br"&lt;/pre&gt;</description>
    <dc:creator>Paulo Roberto Vieira Brandao</dc:creator>
    <dc:date>2012-03-12T21:56:21</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.lighttpd/5335">
    <title>Re: CGI - carriage-return for new lines?</title>
    <link>http://permalink.gmane.org/gmane.comp.web.lighttpd/5335</link>
    <description>&lt;pre&gt;
Thank you Stefan, I don't know HTTP details and I wasn't aware that the
request-body sent to CGI scripts by standard input is directly generated
by the client's user agent.

However, looking back to the CGI specification (*), the request-body is
defined simply as an OCTET stream of data, octet being an undefined
keyword (perhaps it refers to HTTP spec?), without recognizing the
existence of text lines and their possible breaking character sequences.

I wonder if servers are required to pass these OCTETs unaltered or if
they are free to adapt the text encode to the one used by the platform,
of course only in the ambit of text type MIMEs.

(*) request-body section: http://tools.ietf.org/html/rfc3875#page-20


&lt;/pre&gt;</description>
    <dc:creator>Davide Baldini</dc:creator>
    <dc:date>2012-02-28T12:36:15</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.lighttpd/5334">
    <title>Re: CGI - carriage-return for new lines?</title>
    <link>http://permalink.gmane.org/gmane.comp.web.lighttpd/5334</link>
    <description>&lt;pre&gt;Hi,

On 02/28/2012 05:52 AM, Davide Baldini wrote:

If you are talking about writing a CGI script in bash and want to read 
the request body, there is not much lighttpd can do for you - it doesn't 
touch the body (the headers are passed in environment variables)



&lt;/pre&gt;</description>
    <dc:creator>Stefan Bühler</dc:creator>
    <dc:date>2012-02-28T09:40:31</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.lighttpd/5333">
    <title>Re: CGI - carriage-return for new lines?</title>
    <link>http://permalink.gmane.org/gmane.comp.web.lighttpd/5333</link>
    <description>&lt;pre&gt;
Hello Ryan,
as of course you know, HTTP specification has nothing to do with CGI-1.1
specification. I personally read the CGI spec on w3.org and about
&amp;lt;newline&amp;gt; it is open to let the system decide; in particular, it states
that webservers must pay attention to convert HTML headers from the
system's encode of &amp;lt;newline&amp;gt; to CR+LF.

Inside UNIX-based OSs we should use the UNIX encode, not the Windows one.

--
please send me Carbon Copies since I'm not subscribed to the list.


&lt;/pre&gt;</description>
    <dc:creator>Davide Baldini</dc:creator>
    <dc:date>2012-02-28T06:13:16</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.lighttpd/5332">
    <title>Re: CGI - carriage-return for new lines?</title>
    <link>http://permalink.gmane.org/gmane.comp.web.lighttpd/5332</link>
    <description>&lt;pre&gt;
On Feb 27, 2012, at 22:52, Davide Baldini wrote:


The HTTP specification says that lines must be terminated by CRLF.




&lt;/pre&gt;</description>
    <dc:creator>Ryan Schmidt</dc:creator>
    <dc:date>2012-02-28T05:08:20</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.lighttpd/5331">
    <title>CGI - carriage-return for new lines?</title>
    <link>http://permalink.gmane.org/gmane.comp.web.lighttpd/5331</link>
    <description>&lt;pre&gt;I'm writing Bash script to process a stdin caming from lighttpd's CGI. I
noticed that the caming lines carry a trailing carriage-return for
breaking lines, instead of the expected line-feed, and obviously bash
fails to recognize new lines.

The MIME type is "multipart/form-data";
lighttpd -v
lighttpd/1.4.28 (ssl) - a light and fast webserver
Build-Date: Dec 20 2011 22:59:43


&lt;/pre&gt;</description>
    <dc:creator>Davide Baldini</dc:creator>
    <dc:date>2012-02-28T04:52:03</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.lighttpd/5330">
    <title>(unknown)</title>
    <link>http://permalink.gmane.org/gmane.comp.web.lighttpd/5330</link>
    <description>&lt;pre&gt;



&lt;/pre&gt;</description>
    <dc:creator>GASPARD Kévin</dc:creator>
    <dc:date>2012-01-13T01:10:41</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.lighttpd/5329">
    <title>Re: ssl.ciphers vs. ssl.cipher-list</title>
    <link>http://permalink.gmane.org/gmane.comp.web.lighttpd/5329</link>
    <description>&lt;pre&gt;Hi Christian,

On 12/15/2011 12:12 PM, Christian Kujau wrote:

ssl.cipher-list is the correct name, the config examples got fixed in r2817.

Thanks for the report.

Kind Regards,
Stefan


&lt;/pre&gt;</description>
    <dc:creator>Stefan Bühler</dc:creator>
    <dc:date>2011-12-18T14:06:29</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.lighttpd/5328">
    <title>ssl.ciphers vs. ssl.cipher-list</title>
    <link>http://permalink.gmane.org/gmane.comp.web.lighttpd/5328</link>
    <description>&lt;pre&gt;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
&lt;/pre&gt;</description>
    <dc:creator>Christian Kujau</dc:creator>
    <dc:date>2011-12-15T11:12:53</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.lighttpd/5327">
    <title>How to log specifed cookie value in access log?</title>
    <link>http://permalink.gmane.org/gmane.comp.web.lighttpd/5327</link>
    <description>&lt;pre&gt;Hello list members,

I read accesslog.txt and verified that lightty yet supports %C for
logging specified cookie. I chance read the lua module mod_magnet,
http://redmine.lighttpd.net/wiki/lighttpd/Docs:ModMagnet, and tried to
extract specified cookie and append to uri:

&lt;/pre&gt;</description>
    <dc:creator>Kaiwang Chen</dc:creator>
    <dc:date>2011-10-18T13:02:36</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.lighttpd/5326">
    <title>Re: [Q] Comparative Apache directives in Lighttpd  [SOLVED]</title>
    <link>http://permalink.gmane.org/gmane.comp.web.lighttpd/5326</link>
    <description>&lt;pre&gt;Solved.  Comment out the default server.pem settings in the  
/etc/lighttpd/conf-enabled/10-ssl.conf  :-

# /usr/share/doc/lighttpd-doc/ssl.txt

#$SERVER["socket"] == "0.0.0.0:443" {
#    ssl.engine  = "enable"
#    ssl.pemfile = "/etc/lighttpd/server.pem"
#}


&lt;/pre&gt;</description>
    <dc:creator>Simon Loewenthal</dc:creator>
    <dc:date>2011-10-17T14:43:09</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.lighttpd/5325">
    <title>Re: [Q] Comparative Apache directives in Lighttpd  [SOLVED]</title>
    <link>http://permalink.gmane.org/gmane.comp.web.lighttpd/5325</link>
    <description>&lt;pre&gt;I found the answer [RTM]
http://redmine.lighttpd.net/wiki/lighttpd/Docs:SSL
Just concatenate the files together as described in the above URL.

However, I would like to know where the configuration references the
file server.pem?

Starting web server: lighttpd2011-10-17 16:23:15: (network.c.602) SSL:
Private key does not match the certificate public key, reason:
error:02001002:system library:fopen:No such file or directory
/etc/lighttpd/server.pem

I added this:-

$SERVER["socket"] == ":80" {
  $HTTP["host"] =~ "webmail.klunky.co.uk" {
    url.redirect = ( "^/(.*)" =&amp;gt; "https://example.com/$1" )
    server.name                 = "example.com"
  }
}

$SERVER["socket"] == ":443" {
  ssl.engine = "enable"
  ssl.pemfile = "/etc/ssl/private/example.com.concatonated.KEY_CRT.pem"
  ssl.ca-file = "/etc/ssl/certs/startcomCA.concatonated.CA.pem"

$HTTP["host"] == "webmail.example.com" {
    server.name = "webmail.example.com"
  server.document-root = "/web/rc/"
}
}

What I don't quite understand is what happens for sit&lt;/pre&gt;</description>
    <dc:creator>Simon Loewenthal</dc:creator>
    <dc:date>2011-10-17T14:28:08</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.lighttpd/5324">
    <title>[Q] Comparative Apache directives in Lighttpd</title>
    <link>http://permalink.gmane.org/gmane.comp.web.lighttpd/5324</link>
    <description>&lt;pre&gt;Hi there,

I am migrating a server from Apache to Lighttpd.  I have an SSL question.

What it the comparative Lighttpd line for each of  these in Apache?

   SSLEngine on
   SSLProtocol all -SSLv2
   SSLCipherSuite HIGH:MEDIUM
   SSLCertificateFile /etc/ssl/private/example.ssl.crt
   SSLCertificateKeyFile /etc/ssl/private/example.ssl.key
   SSLCertificateChainFile /etc/ssl/certs/startcomIntermediateCA.pem
   SSLCACertificateFile /etc/ssl/certs/startcomCA.pem


Best regards, Simon.

&lt;/pre&gt;</description>
    <dc:creator>Simon Loewenthal</dc:creator>
    <dc:date>2011-10-17T14:09:44</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.lighttpd/5323">
    <title>(unknown)</title>
    <link>http://permalink.gmane.org/gmane.comp.web.lighttpd/5323</link>
    <description>&lt;pre&gt;

&lt;/pre&gt;</description>
    <dc:creator>david</dc:creator>
    <dc:date>2011-09-05T07:15:57</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.lighttpd/5320">
    <title>DOS boxes in Windows 7</title>
    <link>http://permalink.gmane.org/gmane.comp.web.lighttpd/5320</link>
    <description>&lt;pre&gt;Hello list,

I have a project with a web based application, distributed
on a USB-stick. The basic configuration I got from light2go.

It works nicely from Windows 2000 through Vista.

But on Windows 7 I get a console-window ("DOS box") with 
every request. It appears and vanishes quickly, but it is
annoying nevertheless.

I tried some tricks with "start as administrator" and "start
in compatibility mode", but nothing helps.

Do you have any hint for me?

Thanks in advance

Emil


&lt;/pre&gt;</description>
    <dc:creator>Emil Obermayr</dc:creator>
    <dc:date>2011-08-08T13:28:08</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.lighttpd/5316">
    <title>Tudo para seu Bebê, pelo menor preço, só aqui! Roupinhas, Cercados, Berços e muito mais!</title>
    <link>http://permalink.gmane.org/gmane.comp.web.lighttpd/5316</link>
    <description>&lt;pre&gt;Seu cliente de e-mail não pode ler este e-mail.
Para visualizá-lo on-line, por favor, clique aqui:
http://www.mkt3000.com.br/envio/display.php?M=11474082&amp;amp;C=69614b70c1d582fa5bc9e51445d91cc5&amp;amp;S=534&amp;amp;L=116&amp;amp;N=7


Para parar de receber nossos
Emails:http://www.mkt3000.com.br/envio/unsubscribe.php?M=11474082&amp;amp;C=69614b70c1d582fa5bc9e51445d91cc5&amp;amp;L=116&amp;amp;N=534
Email Marketing
&lt;/pre&gt;</description>
    <dc:creator>Walmart.com.br - Parceiro Computer Hobby</dc:creator>
    <dc:date>2011-03-11T20:52:34</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.lighttpd/5314">
    <title>Aparelho de Jantar 99,90 reais.GPS LCD Touchscreen por 338 reais.Aproveite.</title>
    <link>http://permalink.gmane.org/gmane.comp.web.lighttpd/5314</link>
    <description>&lt;pre&gt;Seu cliente de e-mail não pode ler este e-mail.
Para visualizá-lo on-line, por favor, clique aqui:
http://www.mkt3000.com.br/envio/display.php?M=11474082&amp;amp;C=69614b70c1d582fa5bc9e51445d91cc5&amp;amp;S=528&amp;amp;L=116&amp;amp;N=7


Para parar de receber nossos
Emails:http://www.mkt3000.com.br/envio/unsubscribe.php?M=11474082&amp;amp;C=69614b70c1d582fa5bc9e51445d91cc5&amp;amp;L=116&amp;amp;N=528
Email Marketing
&lt;/pre&gt;</description>
    <dc:creator>walmart - Parceiro Computerhobby</dc:creator>
    <dc:date>2011-03-10T02:10:11</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.lighttpd/5313">
    <title>Seguro de Vida, Comodidade a Você e Sua Familia no Momento em que mais Precisa.</title>
    <link>http://permalink.gmane.org/gmane.comp.web.lighttpd/5313</link>
    <description>&lt;pre&gt;Seu cliente de e-mail não pode ler este e-mail.
Para visualizá-lo on-line, por favor, clique aqui:
http://www.mkt3000.com.br/envio/display.php?M=11493361&amp;amp;C=6ff1d9cd3aa9eafb863cf29a640decf3&amp;amp;S=485&amp;amp;L=170&amp;amp;N=46


Para parar de receber nossos
Emails:http://www.mkt3000.com.br/envio/unsubscribe.php?M=11493361&amp;amp;C=6ff1d9cd3aa9eafb863cf29a640decf3&amp;amp;L=170&amp;amp;N=485
Email Marketing
&lt;/pre&gt;</description>
    <dc:creator>Paulo Leal</dc:creator>
    <dc:date>2011-03-04T16:19:55</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.lighttpd/5312">
    <title>Ganhe Cupons e Compre com Descontos...</title>
    <link>http://permalink.gmane.org/gmane.comp.web.lighttpd/5312</link>
    <description>&lt;pre&gt;Seu cliente de e-mail não pode ler este e-mail.
Para visualizá-lo on-line, por favor, clique aqui:
http://www.mkt3000.com.br/envio/display.php?M=7332320&amp;amp;C=0e648cc199b058170be8e51e2468d95d&amp;amp;S=474&amp;amp;L=207&amp;amp;N=45


Para parar de receber nossos
Emails:http://www.mkt3000.com.br/envio/unsubscribe.php?M=7332320&amp;amp;C=0e648cc199b058170be8e51e2468d95d&amp;amp;L=207&amp;amp;N=474
Email Marketing
&lt;/pre&gt;</description>
    <dc:creator>Paulo Leal</dc:creator>
    <dc:date>2011-03-04T02:39:57</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.comp.web.lighttpd">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.comp.web.lighttpd</link>
  </textinput>
</rdf:RDF>

