2010/10/7 <[email protected]>

> Send Cherokee mailing list submissions to
>        [email protected]
>
> To subscribe or unsubscribe via the World Wide Web, visit
>        http://lists.octality.com/listinfo/cherokee
> or, via email, send a message with subject or body 'help' to
>        [email protected]
>
> You can reach the person managing the list at
>        [email protected]
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Cherokee digest..."
>
>
> Today's Topics:
>
>   1. Re: Rewrite rules questions (Rafael Bonifaz)
>   2. Re: perl scripts (oddmuse) (xancorreu)
>   3. Re: perl scripts (oddmuse) (Juan J. Mart?nez)
>   4. Re: Rewrite rules questions (Rafael Bonifaz)
>   5. Re: perl scripts (oddmuse) (xancorreu)
>   6. force http to https (James)
>   7. Re: force http to https (James)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 06 Oct 2010 07:45:34 -0500
> From: Rafael Bonifaz <[email protected]>
> To: Jeff Johnson <[email protected]>
> Cc: [email protected]
> Subject: Re: [Cherokee] Rewrite rules questions
> Message-ID: <[email protected]>
> Content-Type: text/plain; charset="iso-8859-1"
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> El 06/10/10 02:01, Jeff Johnson escribi?:
> > Rafael, Apparently it was easier than I initially thought.  All you
> > have to do is add the appropriate redirection rules to Cherokee.  I
> > posted a quick how-to here:
> >
> http://www.ututech.com/2010/10/configuring-yourls-to-work-with-cherokee-web-server/
> >
> >
> >
> I have not *extensively* tested this, but it seems to work on my box.
> >
>
> Wow, that was fast :). Thanks a lot, I would test it today and came
> back here. Your post should be linked to the yourls wiki.
>
> Best regards,
>
> Rafael
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAkysb24ACgkQ/R157VJtzzFIaQCgqmbx9jmV+XMFrpm/6XLGRa14
> fX4Ani5Wn5bwe0xwrvTRFBvLTPmnbDpN
> =Js8V
> -----END PGP SIGNATURE-----
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://lists.octality.com/pipermail/cherokee/attachments/20101006/a0116e0b/attachment-0001.html
> >
>
> ------------------------------
>
> Message: 2
> Date: Wed, 06 Oct 2010 17:10:11 +0200
> From: xancorreu <[email protected]>
> To: "\"Juan J.\" Mart?nez" <[email protected]>
> Cc: [email protected]
> Subject: Re: [Cherokee] perl scripts (oddmuse)
> Message-ID: <[email protected]>
> Content-Type: text/plain; charset=UTF-8; format=flowed
>
> Al 04/10/10 16:34, En/na Juan J. Mart?nez ha escrit:
> > El lun, 04-10-2010 a las 16:30 +0200, xancorreu escribi?:
> >
> >> [...]
> >>
> >>>
> >>>
> >> I don't think so: thttpd is running with www-data and all is ok.
> >> oddmuse.pl has chown to www-data:www-data.
> >>
> >>
> > I have almost the same configuration in a couple of scripts, and it
> > works perfectly.
> >
> > But I can see a difference, I'm not using "Script Alias" but instead the
> > CGI has the executable bit and starts with the comment that provides the
> > shell the interpreter to run the script (#!/usr/bin/perl).
> >
> > I would try to remove the "Script Alias" part and check the executable
> > bit and starting line of the script.
> >
> Without "Script Alias" oddmuse (current.pl) runs but my wiki.pl does not:
>
> wiki.pl contains are:
> #! /usr/bin/perl
> package OddMuse;
> $DataDir = '/var/www/wiki/wikidata';
> $ConfigFile = '/var/www/wiki/wikicmd/oddmuseconfig';
> do '/var/www/wiki/wikicmd/current.pl';
>
> Why?
>
> Xan.
>
>
> ------------------------------
>
> Message: 3
> Date: Wed, 06 Oct 2010 16:09:53 +0100
> From: "Juan J." Mart?nez <[email protected]>
> To: xancorreu <[email protected]>
> Cc: [email protected]
> Subject: Re: [Cherokee] perl scripts (oddmuse)
> Message-ID: <[email protected]>
> Content-Type: text/plain; charset="UTF-8"
>
> El mi?, 06-10-2010 a las 17:10 +0200, xancorreu escribi?:
> > Al 04/10/10 16:34, En/na Juan J. Mart?nez ha escrit:
> > > El lun, 04-10-2010 a las 16:30 +0200, xancorreu escribi?:
> > >
> > >> [...]
> > >>
> > >>>
> > >>>
> > >> I don't think so: thttpd is running with www-data and all is ok.
> > >> oddmuse.pl has chown to www-data:www-data.
> > >>
> > >>
> > > I have almost the same configuration in a couple of scripts, and it
> > > works perfectly.
> > >
> > > But I can see a difference, I'm not using "Script Alias" but instead
> the
> > > CGI has the executable bit and starts with the comment that provides
> the
> > > shell the interpreter to run the script (#!/usr/bin/perl).
> > >
> > > I would try to remove the "Script Alias" part and check the executable
> > > bit and starting line of the script.
> > >
> > Without "Script Alias" oddmuse (current.pl) runs but my wiki.pl does
> not:
> >
> > wiki.pl contains are:
> > #! /usr/bin/perl
>   ^^
>  Remove those spaces.
>
> Cheers,
>
> Juanjo
>
> --
> jjm's home: http://www.usebox.net/jjm/
> blackshell: http://blackshell.usebox.net/
>  ramble on: http://rambleon.usebox.net/
>
>
>
>
> ------------------------------
>
> Message: 4
> Date: Wed, 06 Oct 2010 10:16:14 -0500
> From: Rafael Bonifaz <[email protected]>
> To: Jeff Johnson <[email protected]>
> Cc: [email protected]
> Subject: Re: [Cherokee] Rewrite rules questions
> Message-ID: <[email protected]>
> Content-Type: text/plain; charset="iso-8859-1"
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> El 06/10/10 02:01, Jeff Johnson escribi?:
> > Rafael, Apparently it was easier than I initially thought.  All you
> > have to do is add the appropriate redirection rules to Cherokee.  I
> > posted a quick how-to here:
> >
> http://www.ututech.com/2010/10/configuring-yourls-to-work-with-cherokee-web-server/
> >
> >
> >
> I have not *extensively* tested this, but it seems to work on my box.
>
>
> It seems to work perfect:
>
> http://bonifaz.ec/yourlscherokee
>
> Thank you,
>
> Rafael
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAkyskr4ACgkQ/R157VJtzzFASwCgmLHu93pk0m/aY9vwcm+7OBJT
> fIkAniFfGSXNRFZYldV/bicbMACXwThu
> =pFRx
> -----END PGP SIGNATURE-----
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://lists.octality.com/pipermail/cherokee/attachments/20101006/721f404f/attachment-0001.html
> >
>
> ------------------------------
>
> Message: 5
> Date: Wed, 06 Oct 2010 19:04:19 +0200
> From: xancorreu <[email protected]>
> To: "\"Juan J.\" Mart?nez" <[email protected]>
> Cc: [email protected]
> Subject: Re: [Cherokee] perl scripts (oddmuse)
> Message-ID: <[email protected]>
> Content-Type: text/plain; charset=UTF-8; format=flowed
>
> En/na Juan J. Mart?nez ha escrit:
> >>
> >> Without "Script Alias" oddmuse (current.pl) runs but my wiki.pl does
> not:
> >>
> >> wiki.pl contains are:
> >> #! /usr/bin/perl
> >>
> >    ^^
> >  Remove those spaces.
> >
> > Cheers,
> >
> > Juanjo
> >
> >
> Yes, it works. Thanks a lot,
> Xan.
>
>
>
> ------------------------------
>
> Message: 6
> Date: Wed, 6 Oct 2010 14:50:12 -0400
> From: James <[email protected]>
> To: [email protected]
> Subject: [Cherokee] force http to https
> Message-ID:
>        <[email protected]>
> Content-Type: text/plain; charset=ISO-8859-1
>
> All,
>
> I've been a long time Cherokee fan -- many thanks to the developers
> who spend so many hours improving such an awesome product. I have a
> rather simple question and am hoping someone can help me out.
>
> I'm trying to force traffic to use HTTPS instead of HTTP. To do so I'm
> following the following recipe:
>
> http://www.cherokee-project.com/doc/cookbook_http_to_https.html
>
> As an example, I have http://webtools.example.com ->
> https://webtools.example.com.
>
> So I set up a new rule that looks as follows:
>
> vserver!2!rule!140!disabled = 0
> vserver!2!rule!140!handler = redir
> vserver!2!rule!140!handler!rewrite!1!regex = /(.*)$
> vserver!2!rule!140!handler!rewrite!1!show = 1
> vserver!2!rule!140!handler!rewrite!1!substring = https://${host}/$1
> vserver!2!rule!140!match = directory
> vserver!2!rule!140!match!directory = /
> vserver!2!rule!140!match!final = 1
> vserver!2!rule!140!match!fullpath!1 = /
> vserver!2!rule!140!only_secure = 0
>
> As far as I can tell this is the correct way to do this. The problem,
> however, is the '/' directory match. When I set the root directory to
> something like /tools, then going to http://webtools.example.com/tools
> will forward to HTTPS. However, I want *all*
> http://webtools.example.com/ traffic to be forwarded to HTTPS.
>
> When I leave my root directory as '/', the connection fails. Firefox
> throws an error (we presumably have a loop here).
>
> -->8--
>
> The page isn't redirecting properly
>
> Firefox has detected that the server is redirecting the request for
> this address in a way that will never complete.
>
> *   This problem can sometimes be caused by disabling or refusing to
> accept cookies.
>
> --8<--
>
> I'm out of ideas. I know I had this working in the past but can't seem
> to simulate the behavior. Any thoughts / ideas / help would be greatly
> appreciated!
>
> Thanks!
> -james
>
>
> ------------------------------
>
> Message: 7
> Date: Wed, 6 Oct 2010 16:32:30 -0400
> From: James <[email protected]>
> To: [email protected]
> Subject: Re: [Cherokee] force http to https
> Message-ID:
>        
> <[email protected]<lbzzgeq%[email protected]>
> >
> Content-Type: text/plain; charset=ISO-8859-1
>
> Folks,
>
> When I manually execute /usr/sbin/cherokee, I see that the process is
> panicing due to something in the configuration in the configuration I
> pasted before.
>
> Here's the output:
>
> # /usr/sbin/cherokee
> Cherokee Web Server 1.0.8 (Oct  5 2010): Listening on ports ALL:80,
> ALL:443(TLS), with TLS support via libssl, IPv6 enabled, using epoll, 4096
> fds system limit, max. 2041 connections, caching I/O, 30 threads, 68
> connections per thread, standard scheduling policy
> Cherokee feels panic!
> sendmail: Cannot open mail:25
> PID 3331: received a signal=6
> Cherokee Web Server 1.0.8 (Oct  5 2010): Listening on ports ALL:80,
> ALL:443(TLS), with TLS support via libssl, IPv6 enabled, using epoll, 4096
> fds system limit, max. 2041 connections, caching I/O, 30 threads, 68
> connections per thread, standard scheduling policy
> Cherokee feels panic!
> sendmail: Cannot open mail:25
> PID 3381: received a signal=6
> Cherokee Web Server 1.0.8 (Oct  5 2010): Listening on ports ALL:80,
> ALL:443(TLS), with TLS support via libssl, IPv6 enabled, using epoll, 4096
> fds system limit, max. 2041 connections, caching I/O, 30 threads, 68
> connections per thread, standard scheduling policy
>
> Thoughts?
>
> -james
>
>
>
> On Wed, Oct 6, 2010 at 2:50 PM, James <[email protected]> wrote:
> > All,
> >
> > I've been a long time Cherokee fan -- many thanks to the developers
> > who spend so many hours improving such an awesome product. I have a
> > rather simple question and am hoping someone can help me out.
> >
> > I'm trying to force traffic to use HTTPS instead of HTTP. To do so I'm
> > following the following recipe:
> >
> > http://www.cherokee-project.com/doc/cookbook_http_to_https.html
> >
> > As an example, I have http://webtools.example.com ->
> > https://webtools.example.com.
> >
> > So I set up a new rule that looks as follows:
> >
> > vserver!2!rule!140!disabled = 0
> > vserver!2!rule!140!handler = redir
> > vserver!2!rule!140!handler!rewrite!1!regex = /(.*)$
> > vserver!2!rule!140!handler!rewrite!1!show = 1
> > vserver!2!rule!140!handler!rewrite!1!substring = https://${host}/$1
> > vserver!2!rule!140!match = directory
> > vserver!2!rule!140!match!directory = /
> > vserver!2!rule!140!match!final = 1
> > vserver!2!rule!140!match!fullpath!1 = /
> > vserver!2!rule!140!only_secure = 0
> >
> > As far as I can tell this is the correct way to do this. The problem,
> > however, is the '/' directory match. When I set the root directory to
> > something like /tools, then going to http://webtools.example.com/tools
> > will forward to HTTPS. However, I want *all*
> > http://webtools.example.com/ traffic to be forwarded to HTTPS.
> >
> > When I leave my root directory as '/', the connection fails. Firefox
> > throws an error (we presumably have a loop here).
> >
> > -->8--
> >
> > The page isn't redirecting properly
> >
> > Firefox has detected that the server is redirecting the request for
> > this address in a way that will never complete.
> >
> > * ? This problem can sometimes be caused by disabling or refusing to
> > accept cookies.
> >
> > --8<--
> >
> > I'm out of ideas. I know I had this working in the past but can't seem
> > to simulate the behavior. Any thoughts / ideas / help would be greatly
> > appreciated!
> >
> > Thanks!
> > -james
> >
>
>
> ------------------------------
>
> _______________________________________________
> Cherokee mailing list
> [email protected]
> http://lists.octality.com/listinfo/cherokee
>
>
> End of Cherokee Digest, Vol 28, Issue 7
> ***************************************
>



-- 
-------------------------------------------
Pozdrawiam,
Dariusz PAWLAK
email: [email protected]
tel. +48 693 911 792
_______________________________________________
Cherokee mailing list
[email protected]
http://lists.octality.com/listinfo/cherokee

Reply via email to