The recipe is no good. Instead, make a rule, type SSL and NOT it. Run the regex on that rule.
Else you run into an infinite redirection. On Wed, Oct 6, 2010 at 22:32, James <[email protected]> wrote: > 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 > _______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
