Jonathan | 1 Feb 03:31 2006

memcache / mod_cml

I have a question -

i am currently running this:
	lighttpd - frontend server *:80
	certain directories on certain host/urls are sent to:
		apache2/modperl - backend server localhost:8000

some entire pages for apache2/modperl are rendered as such

	check memcache to see if we have a pre-rendered version
	if yes:
		display cache
	if no:
		render page
		display page
		store page in cache w/a 30min ttl
	end

looking at the lighttpd docs earlier, i noticed some mod_cml stuff  
and memcache support

does anyone know if it would be possible to do this :

	for lighttpd url:
		check memcache to see if we have a pre-rendered  version
		if yes:
			display cache
		if no:
			pass on to mod_perl
			mod_perl renders page
(Continue reading)

Jan Kneschke | 1 Feb 12:42 2006
Picon

Re: Patch to src/server.c to provide debug info if fam fails

On Mon, Jan 23, 2006 at 09:59:55AM +0000, Ævar Arnfjörð Bjarmason wrote:
> I was having some issues with lighttpd after compiling it --with-fam
> when I had server.stat-cache-engine = "fam" in my lighttpd.conf. I
> turned out that I had just forgotten to start famd and that lighttpd
> was failing to connect to it, however lighttpd wrote nothing in the
> error log about this. The following patch modifies server.c to write a
> message to the log when this happens.

Ok, it is applied and the ticket is closed.

    Jan

--

-- 
Jan Kneschke                                     http://jan.kneschke.de/
Perhaps you want to say 'thank you, jan':    http://jk.123.org/wishlist/

Jan Kneschke | 1 Feb 13:03 2006
Picon

Re: there is nothing about dir-listing.encoding in docs

On Fri, Jan 20, 2006 at 07:04:48PM +0300, Roman Shiryaev wrote:
> hi,
> 
> I've discoved that description of one option is not presented in
> the official documentation:
> http://www.lighttpd.net/documentation/configuration.html
> 
> I'm talking about `dir-lising.encoding'.
> 
> Somebody reopened a related bug report 3 months ago:
> http://trac.lighttpd.net/trac/ticket/136
> 
> but nothing has changed since 16 October 2005.
> 
> Please fix it.

fixed in changeset 978.

> Thanks.
> 
    Jan

--

-- 
Jan Kneschke                                     http://jan.kneschke.de/
Perhaps you want to say 'thank you, jan':    http://jk.123.org/wishlist/

John D. Mitchell | 1 Feb 18:16 2006
Picon

mod_proxy and other HTTP methods?

I read in the docs that lighty only directly supports the HTTP methods
HEAD, GET, and POST.

What about for mod_proxy?  I.e., will mod_proxy pass through all of
the other HTTP methods such as PUT, DELETE, etc.?

Thanks,
John

Jan Kneschke | 1 Feb 18:21 2006
Picon

Re: mod_proxy and other HTTP methods?

On Wed, Feb 01, 2006 at 09:16:14AM -0800, John D. Mitchell wrote:
> I read in the docs that lighty only directly supports the HTTP methods
> HEAD, GET, and POST.

Oops, where have you read it ? I'll updated it. Through mod_webdav we
also know about the methods below

> What about for mod_proxy?  I.e., will mod_proxy pass through all of
> the other HTTP methods such as PUT, DELETE, etc.?

Proxy knows about the methods:

static keyvalue http_methods[] = {
        { HTTP_METHOD_GET,  "GET" },
        { HTTP_METHOD_POST, "POST" },
        { HTTP_METHOD_HEAD, "HEAD" },
        { HTTP_METHOD_PROPFIND, "PROPFIND" },
        { HTTP_METHOD_PROPPATCH, "PROPPATCH" },
        { HTTP_METHOD_REPORT, "REPORT" },
        { HTTP_METHOD_OPTIONS, "OPTIONS" },
        { HTTP_METHOD_MKCOL, "MKCOL" },
        { HTTP_METHOD_PUT, "PUT" },
        { HTTP_METHOD_DELETE, "DELETE" },
        { HTTP_METHOD_COPY, "COPY" },
        { HTTP_METHOD_MOVE, "MOVE" },
        { HTTP_METHOD_LABEL, "LABEL" },
        { HTTP_METHOD_CHECKOUT, "CHECKOUT" },
        { HTTP_METHOD_CHECKIN, "CHECKIN" },
        { HTTP_METHOD_UNCHECKOUT, "UNCHECKOUT" },
        { HTTP_METHOD_VERSION_CONTROL, "VERSION-CONTROL" },
(Continue reading)

John D. Mitchell | 1 Feb 18:26 2006
Picon

Re: mod_proxy and other HTTP methods?

On 2/1/06, Jan Kneschke <jan <at> kneschke.de> wrote:
> On Wed, Feb 01, 2006 at 09:16:14AM -0800, John D. Mitchell wrote:
> > I read in the docs that lighty only directly supports the HTTP methods
> > HEAD, GET, and POST.
>
> Oops, where have you read it ? I'll updated it. Through mod_webdav we
> also know about the methods below

The HTTP/1.1 features & compliance sections of:
http://www.lighttpd.net/modules/

> > What about for mod_proxy?  I.e., will mod_proxy pass through all of
> > the other HTTP methods such as PUT, DELETE, etc.?
>
> Proxy knows about the methods:
>
> static keyvalue http_methods[] = {
>         { HTTP_METHOD_GET,  "GET" },
>         { HTTP_METHOD_POST, "POST" },
>         { HTTP_METHOD_HEAD, "HEAD" },
>         { HTTP_METHOD_PROPFIND, "PROPFIND" },
>         { HTTP_METHOD_PROPPATCH, "PROPPATCH" },
>         { HTTP_METHOD_REPORT, "REPORT" },
>         { HTTP_METHOD_OPTIONS, "OPTIONS" },
>         { HTTP_METHOD_MKCOL, "MKCOL" },
>         { HTTP_METHOD_PUT, "PUT" },
>         { HTTP_METHOD_DELETE, "DELETE" },
>         { HTTP_METHOD_COPY, "COPY" },
>         { HTTP_METHOD_MOVE, "MOVE" },
>         { HTTP_METHOD_LABEL, "LABEL" },
(Continue reading)

Ryan Schmidt | 1 Feb 19:33 2006

mod_proxy and Subversion? (was Re: mod_proxy and other HTTP methods?)

On Feb 1, 2006, at 18:21, Jan Kneschke wrote:

>> What about for mod_proxy?  I.e., will mod_proxy pass through all of
>> the other HTTP methods such as PUT, DELETE, etc.?
>
> Proxy knows about the methods:
>
> static keyvalue http_methods[] = {
>         { HTTP_METHOD_GET,  "GET" },
>         { HTTP_METHOD_POST, "POST" },
>         { HTTP_METHOD_HEAD, "HEAD" },
>         { HTTP_METHOD_PROPFIND, "PROPFIND" },
>         { HTTP_METHOD_PROPPATCH, "PROPPATCH" },
>         { HTTP_METHOD_REPORT, "REPORT" },
>         { HTTP_METHOD_OPTIONS, "OPTIONS" },
>         { HTTP_METHOD_MKCOL, "MKCOL" },
>         { HTTP_METHOD_PUT, "PUT" },
>         { HTTP_METHOD_DELETE, "DELETE" },
>         { HTTP_METHOD_COPY, "COPY" },
>         { HTTP_METHOD_MOVE, "MOVE" },
>         { HTTP_METHOD_LABEL, "LABEL" },
>         { HTTP_METHOD_CHECKOUT, "CHECKOUT" },
>         { HTTP_METHOD_CHECKIN, "CHECKIN" },
>         { HTTP_METHOD_UNCHECKOUT, "UNCHECKOUT" },
>         { HTTP_METHOD_VERSION_CONTROL, "VERSION-CONTROL" },
>         { HTTP_METHOD_CONNECT, "CONNECT" },
>
>         { HTTP_METHOD_UNSET, NULL }
> };

(Continue reading)

Jonathan Vanasco | 1 Feb 20:00 2006

Re: mod_proxy and Subversion? (was Re: mod_proxy and other HTTP methods?)


On Feb 1, 2006, at 1:33 PM, Ryan Schmidt wrote:
> Oh really! And I thought proxy only supported GET and POST, and  
> that that was the reason I couldn't proxy Subversion requests. But  
> if these methods are all supported, then there must be different  
> reason Subversion doesn't work.

No one can proxy subversion to apache yet

Look in the list archives over the past 3 weeks - it comes up a lot.   
There are a ton of suggestions and recommended protocols in there.

I believe jan is working on some of the issues to make it work  
eventually.

Personally, i just run SVN on a virtual host bound to *:8011  
( 127.0.0.1:8000->127.0.0.1:8010 are used by other projects) and  
connect to the SVN repo directly

when you need to switch from :8011 to :80 in the future, all you need  
to do is:

	svn switch /path/to/local www.new.url

Chris Adams | 2 Feb 00:44 2006
Picon

Patch to add banner/tag to dirlisting (and performace question)

I wrote a patch that optionally adds a banner at the top and a tag at
the bottom of directory listings (you can see a tag with this patch at
http://mirror.hiwaay.net/).  I've attached the patch to this message.

Has anyone else seen performance problems with listings of large
directories?  I host a CPAN mirror, and even with caching with
server.stat-cache-engine = "fam", one hit listing a long directory can
block other connections.

On Linux and some BSDs there is a dirfd() function that would allow
select/poll on directory reading.  Alternately, directory reading could
fork a child to do the read.

--

-- 
Chris Adams <cmadams <at> hiwaay.net>
Systems and Network Administrator - HiWAAY Internet Services
I don't speak for anybody but myself - that's enough trouble.
diff -urN lighttpd-1.4.9-dist/src/mod_dirlisting.c lighttpd-1.4.9/src/mod_dirlisting.c
--- lighttpd-1.4.9-dist/src/mod_dirlisting.c	2006-01-12 16:00:45.000000000 -0600
+++ lighttpd-1.4.9/src/mod_dirlisting.c	2006-01-27 22:05:42.000000000 -0600
 <at>  <at>  -59,6 +59,8  <at>  <at> 

 	buffer *external_css;
 	buffer *encoding;
+	buffer *banner_file;
+	buffer *tag_file;
 } plugin_config;

(Continue reading)

Xuefer | 2 Feb 04:14 2006
Picon

Re: Patch to add banner/tag to dirlisting (and performace question)

On 2/2/06, Chris Adams <cmadams <at> hiwaay.net> wrote:
> I wrote a patch that optionally adds a banner at the top and a tag at
> the bottom of directory listings (you can see a tag with this patch at
> http://mirror.hiwaay.net/).  I've attached the patch to this message.
this is better done after filter system is on svn. but no idea how
many more days to wait...

Gmane