http://blog.gmane.org/gmane.comp.web.cherokee.general hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://permalink.gmane.org/gmane.comp.web.cherokee.general/8853 <pre>I tried both "internal" and "external" with the same effect. "external" has the debugging advantage to show the result of substitution. Nginx and lighttpd are based on original concepts, different from Apache. * lightpd: You regexp-match on the URL and you tell that such initial URL part is related to such document root, e.g.:      $HTTP["url"] =~ "^/LXR_signature/" {             alias.url += ( "/LXR_signature/DB_id" =&gt; "common_LXR_root_directory" )      } and there is another directive to name the files which are scripts. *nginx: There is no notion of "master" DocumentRoot and Alias as in Apache. Every URL can be individually diverted to its own root. Of course in the simplest case, this is equivalent to DocumentRoot or Cherokee's directory rule or default rule. Part of an URL is regexp-matched by a location directive and you tell what you want to do with the bits without rewrite, e.g.:     server { ...         location ~ ^/LXR_signature/[^/]+(.*)$ {             alias /LXR_root_directory/$1 ;     # for ordinary files like .css or images             location ~ ^(/LXR_signature/[^/]+/)(script_names) {                 set $virtroot $1;                 set $scriptname $2;                 alias /LXR_root_directory;                 include fastcgi.conf;                 fastcgi_param SCRIPT_FILENAME $document_root$scriptname;   # compute which script to launch                 fastcgi_param SCRIPT_NAME $virtroot$scriptname; # unaltered CGI variable                 fastcgi_pass unix://...;             }         }     } My idea was to mimic nginx' "action" block. Unhappily, I could not fancy how to simultaneously "untweak" the initial URL part and launch the correct script. I had to break it into two separate rules. The first one identifies the LXR service and removes DB_id to provide an "ordinary" script path, but doing so I lose DB_id. The second one is a common directory rule with CGI handler, but since the URI has changed the called script fails because it takes a segment of the web directory as the DB_id. Anyway, considering the tweaks needed to port LXR on various web servers, I'm more and more convinced that putting the DB_id in the middle of the web directory name (exactly, just before the script name) was a bad design choice (but ages ago, you had Apache - full stop). That information belongs in the script parameters, maybe as a root for PATH_INFO. Notwithstanding the compatibility issue with existing LXR sites, redesigning this needs a lot of effort (first for a neat design, next in trying not to break the core code). Thus if you know the name of a Cherokee variable, like nginx' $originaluri, this could temporarily solve the problem. Thanks for your answers and your patience. ________________________________ De : Daniel Lo Nigro &lt;lists&lt; at &gt;dan.cx&gt; À : Anfré Littoz &lt;page74010-chrk&lt; at &gt;yahoo.fr&gt; Cc : cherokee List &lt;Cherokee&lt; at &gt;lists.octality.com&gt; Envoyé le : Mercredi 1 mai 2013 15h03 Objet : Re: [Cherokee] Migration from Apache to Cherokee: URI tweaking Hmm I thought rewrite rules shouldn't change the URI if they're marked as "internal". Does LXR have instructions for Nginx or Lighttpd? If so, you should be able to convert those rules to Cherokee rules. Apache has so many configuration options that sometimes it's hard to find the exact match._______________________________________________ Cherokee mailing list Cherokee&lt; at &gt;lists.octality.com http://lists.octality.com/listinfo/cherokee </pre> Anfré Littoz 2013-05-01T15:05:36 http://permalink.gmane.org/gmane.comp.web.cherokee.general/8852 <pre>Hmm I thought rewrite rules shouldn't change the URI if they're marked as "internal". Does LXR have instructions for Nginx or Lighttpd? If so, you should be able to convert those rules to Cherokee rules. Apache has so many configuration options that sometimes it's hard to find the exact match. On Wed, May 1, 2013 at 10:57 PM, Anfré Littoz &lt;page74010-chrk&lt; at &gt;yahoo.fr&gt;wrote: _______________________________________________ Cherokee mailing list Cherokee&lt; at &gt;lists.octality.com http://lists.octality.com/listinfo/cherokee </pre> Daniel Lo Nigro 2013-05-01T13:03:46 http://permalink.gmane.org/gmane.comp.web.cherokee.general/8851 <pre>Yes, this is a rewrite rule and consequently it changes the URI. What I need is a rule, which can be flagged "final", causing execution of a CGI script whose home directory is known (e;g. /cgi-bin) and whose name and eventually arguments are taken from the URI ($x substitutions) while the environment variables SERVER_NAME, SCRIPT_NAME, ... are set from the original URI. From the documentation, I'm afraid this is not possible with Cherokee. The alternate solution would be to remove DB_id from the "script web path" part since this was a bad design decision as it mixes script path and argument but this involves a major rewrite of LXR initialisation and configuration. Maybe this is the wise direction since it could greatly simplify integration with web servers and allow for more server candidates. ajl ________________________________ De : Daniel Lo Nigro &lt;lists&lt; at &gt;dan.cx&gt; À : cherokee List &lt;Cherokee&lt; at &gt;lists.octality.com&gt; Envoyé le : Mercredi 1 mai 2013 14h33 Objet : Re: [Cherokee] Migration from Apache to Cherokee: URI tweaking I haven't used Cherokee for a while, but this is known as a rewrite rule ("internal" redirect). _______________________________________________ Cherokee mailing list Cherokee&lt; at &gt;lists.octality.com http://lists.octality.com/listinfo/cherokee_______________________________________________ Cherokee mailing list Cherokee&lt; at &gt;lists.octality.com http://lists.octality.com/listinfo/cherokee </pre> Anfré Littoz 2013-05-01T12:57:09 http://permalink.gmane.org/gmane.comp.web.cherokee.general/8850 <pre>I haven't used Cherokee for a while, but this is known as a rewrite rule ("internal" redirect). On Wed, May 1, 2013 at 8:27 PM, Anfré Littoz &lt;page74010-chrk&lt; at &gt;yahoo.fr&gt;wrote: _______________________________________________ Cherokee mailing list Cherokee&lt; at &gt;lists.octality.com http://lists.octality.com/listinfo/cherokee </pre> Daniel Lo Nigro 2013-05-01T12:33:43 http://permalink.gmane.org/gmane.comp.web.cherokee.general/8849 <pre>Hi, Don't know if this the proper place for such a question, so excuse me if this is considered as "noise". I'm presently testing Cherokee as an alternative to Apache for the LXR project (see http://lxr.sourceforge.net). As long as I use elementary LXR configuration features, it works fine. But, when I come to try to serve several databases (for short, database is the closest ordinary concept equivalent to its "service") with a single application instance, a trick is played on the URI, which I can't fancy how to convert. LXR is driver by this kind of URI: http://hostname/LXR_service_signature/DB_id/script_file/path_for_script?arguments i.e. an argument-like is interspersed inside the web-path for the script. Under Apache, directive AliasMatch strips off this information and simultaneously routes the request to an alternate document root. The important point is the original URI is not changed and available for parsing unaltered by the script which retrieves the DB_id. In my conversion attempt, I used either a directory rule (on LXR_service_signature) or regexp rule, both with a redirect handler to remove the DB_id and other non-path related bits. Unhappily, this rewrites the URI and defeats the script processing which no longer can retrieve the DB_id. Does there exist in Cherokee a means to launch a script whose command line is generated from groups ($1, $2, ...) captured by the regexp-based rule so that the URI is unaltered (environment variables reflect the initial URI)? ajl _______________________________________________ Cherokee mailing list Cherokee&lt; at &gt;lists.octality.com http://lists.octality.com/listinfo/cherokee </pre> Anfré Littoz 2013-05-01T10:27:40 http://permalink.gmane.org/gmane.comp.web.cherokee.general/8848 <pre>Hi, For a very long time, I'm trying to maintain some rules and handlers that are not part of the main cherokee distribution and since we are currently still focused on solving bugs opposed to introducing more, new features get a bitrotten over time. Since Alvaro has suggested the following page, me git n00b, was already experimenting with it. To my suprise with great success, I understood what I was doing, and it looked pretty on the network page as well. &lt;http://nvie.com/posts/a-successful-git-branching-model/&gt; I started to work to get my older features in a more recent Cherokee version and put them in separate branches which it would pull locally for a deployment. I have just placed some new code on github that might be interesting for more people. Do consider it experimental and not tuned for any real world high performance scenario, but very useful for any service that implements DBslayer, or some custom API. &lt;https://github.com/cherokee/webserver/tree/rule_fairuse&gt; It basically allows to count (based on unique IP address) each request that passed by the rule. The rule will match if the predefined limit has been exceeded. Stefan </pre> Stefan de Konink 2013-04-29T13:59:07 http://permalink.gmane.org/gmane.comp.web.cherokee.general/8847 <pre>http://cherokee-project.com/community.html 404; linked from http://cherokee-project.com/contribute.html On Apr 27, 2013, at 6:00 AM, cherokee-request&lt; at &gt;lists.octality.com wrote: _______________________________________________ Cherokee mailing list Cherokee&lt; at &gt;lists.octality.com http://lists.octality.com/listinfo/cherokee </pre> vacant server 2013-04-27T11:50:41 http://permalink.gmane.org/gmane.comp.web.cherokee.general/8846 <pre>Alvaro, perhaps cherokee-project.com should be using an A record for Github as per their docs for Github Pages on a root domain. --- Regards, Daniel Sent from my phone - please excuse any typos. On 27/04/2013 9:13 AM, "MATSUU Takuto" &lt;matsuu&lt; at &gt;gmail.com&gt; wrote: _______________________________________________ Cherokee mailing list Cherokee&lt; at &gt;lists.octality.com http://lists.octality.com/listinfo/cherokee </pre> Daniel Lo Nigro 2013-04-27T01:11:01 http://permalink.gmane.org/gmane.comp.web.cherokee.general/8845 <pre>Hi. cherokee-project.com displays frames with www.cherokee-project.com. www.cherokee-project redirects to cherokee-project.com. It seems that redirect loop. thanks, matsuu 2013/4/26 Alvaro Lopez Ortega &lt;alvaro&lt; at &gt;alobbs.com&gt; _______________________________________________ Cherokee mailing list Cherokee&lt; at &gt;lists.octality.com http://lists.octality.com/listinfo/cherokee </pre> MATSUU Takuto 2013-04-26T23:13:08 http://permalink.gmane.org/gmane.comp.web.cherokee.general/8844 <pre>Thank you very much Makuto. It should be fixed now. All the best, Alvaro On Fri, Apr 26, 2013 at 4:16 PM, MATSUU Takuto &lt;matsuu&lt; at &gt;gmail.com&gt; wrote: </pre> Alvaro Lopez Ortega 2013-04-26T14:24:24 http://permalink.gmane.org/gmane.comp.web.cherokee.general/8843 <pre>Oh yeah, I totally forgot about that. As per https://help.github.com/articles/setting-up-a-custom-domain-with-pages, Github support using an A record for root domains (204.232.175.78). On Sat, Apr 27, 2013 at 12:16 AM, MATSUU Takuto &lt;matsuu&lt; at &gt;gmail.com&gt; wrote: _______________________________________________ Cherokee mailing list Cherokee&lt; at &gt;lists.octality.com http://lists.octality.com/listinfo/cherokee </pre> Daniel Lo Nigro 2013-04-26T14:18:24 http://permalink.gmane.org/gmane.comp.web.cherokee.general/8842 <pre>Hi. To use CNAME on root domain is invalid as RFC. It has many troubles. http://blog.cherokee-project.com/ 404 http://planet.cherokee-project.com/ 404 http://forum.cherokee-project.com/ 404 MX record: none. I propose to use www.cherokee-project.com. IN CNAME cherokee.github.io. cf. http://superuser.com/questions/264913/cant-set-example-com-as-a-cname-record thanks, matsuu 2013/4/19 Alvaro Lopez Ortega &lt;alvaro&lt; at &gt;alobbs.com&gt; _______________________________________________ Cherokee mailing list Cherokee&lt; at &gt;lists.octality.com http://lists.octality.com/listinfo/cherokee </pre> MATSUU Takuto 2013-04-26T14:16:23 http://permalink.gmane.org/gmane.comp.web.cherokee.general/8841 <pre>Great stuff!! On Fri, Apr 19, 2013 at 12:06 PM, Daniel Lo Nigro &lt;lists&lt; at &gt;dan.cx&gt; wrote: </pre> Alvaro Lopez Ortega 2013-04-19T11:14:12 http://permalink.gmane.org/gmane.comp.web.cherokee.general/8840 <pre>Good work people! El 19/04/13 12:06, Daniel Lo Nigro escribió: _______________________________________________ Cherokee mailing list Cherokee&lt; at &gt;lists.octality.com http://lists.octality.com/listinfo/cherokee </pre> Alvaro G. [Andor] 2013-04-19T10:10:15 http://permalink.gmane.org/gmane.comp.web.cherokee.general/8839 <pre>http://cherokee-project.com/ is now live on Github Pages. Awesome :) On Fri, Apr 19, 2013 at 12:53 PM, Daniel Lo Nigro &lt;lists&lt; at &gt;dan.cx&gt; wrote: _______________________________________________ Cherokee mailing list Cherokee&lt; at &gt;lists.octality.com http://lists.octality.com/listinfo/cherokee </pre> Daniel Lo Nigro 2013-04-19T10:06:48 http://permalink.gmane.org/gmane.comp.web.cherokee.general/8838 <pre>Thanks Alvaro, I just need someone to merge this commit and then the CNAME should work :) https://github.com/cherokee/cherokee.github.com/pull/6 On Fri, Apr 19, 2013 at 12:21 PM, Alvaro Lopez Ortega &lt;alvaro&lt; at &gt;alobbs.com&gt;wrote: _______________________________________________ Cherokee mailing list Cherokee&lt; at &gt;lists.octality.com http://lists.octality.com/listinfo/cherokee </pre> Daniel Lo Nigro 2013-04-19T02:53:13 http://permalink.gmane.org/gmane.comp.web.cherokee.general/8837 <pre>On Fri, Apr 12, 2013 at 8:14 PM, M. David Peterson &lt;m.david&lt; at &gt;3rdandurban.com&gt;wrote: The branch with GoPro's modifications based on v1.2.101 =&gt; https://github.com/cherokee/webserver/tree/go-pro-embedded-cherokee-server--v1.2.101-base Same modifications merged with the current HEAD of master =&gt; https://github.com/cherokee/webserver/tree/go-pro-embedded-cherokee-server--master-base Tag for v.1.2.101 with GoPro modifications =&gt; https://github.com/cherokee/webserver/tree/v1.2.101-GoPro </pre> M. David Peterson 2013-04-18T02:18:06 http://permalink.gmane.org/gmane.comp.web.cherokee.general/8836 <pre>at all. I hadn't thought about the "ps aux" command and their gossip behaviour ;) So I think this would be a good option (where -P prompts for a password): echo "mypassword" | ./cherokee-admin-launcher -P another option is to use some pam authentication (or even use the passwd file) at http request for authentication, but this would be a little more complicate and, by now, I don't masters the cherokee code. To do the first idea (the -P one) I believe this should be done: * we only need to change the https://github.com/cherokee/webserver/blob/master/cherokee/main_admin.c file * add a help string at "print_help()" function * at "process_parameters()": add "P" option. At "P" case, set "unsecure" to "1" and "password" to the inputted one (both are globals). It's right? Some questions: 1) if "unsecure" is set to 1, then the code won't rewrite the password, but at line 285 it also won't use the user-defined password. So I guess that I have to change this too. It's right? 2) if I launch the cherokee-admin with the unsecure option at command line (with the -u option) so I can define the user and password by adding this lines at config file (cherokee.conf)? 1!auth = authlist 1!auth!methods = digest 1!auth!realm = Cherokee-admin 1!auth!list!1!user = myuser 1!auth!list!1!password = mypassword 3) Where the "cherokee_buffer_t" structure are defined? To set a password I need to use the cherokee_buffer_add_char() and write char by char or there some other option to do this? PS: my english is awful so if someone don't understand something that I wrote, please tell me so I can reformulate the question ;) Thanks, -- Daniel Loureiro ------------------------------ _______________________________________________ Cherokee mailing list Cherokee&lt; at &gt;lists.octality.com http://lists.octality.com/listinfo/cherokee </pre> Daniel Loureiro 2013-04-17T10:41:16 http://permalink.gmane.org/gmane.comp.web.cherokee.general/8835 <pre>...what you could do, is prompt for a password in that function, and read it from the commandline. Stefan </pre> Stefan de Konink 2013-04-17T09:29:41 http://permalink.gmane.org/gmane.comp.web.cherokee.general/8834 <pre> On Wed, 17 Apr 2013, Daniel Loureiro wrote: &lt;https://github.com/cherokee/webserver/blob/master/cherokee/main_admin.c#L197&gt; The -u option makes it unsecure, a potential password could be added using another option. Since that is the place to check for (un)secure, I guess that place could also be used to assign the defined password instead. I do want to warn you though, this type of configuration is not "secure" at all. ps aux | grep cherokee-admin ...will show it. Stefan </pre> Stefan de Konink 2013-04-17T09:27:35 http://permalink.gmane.org/gmane.comp.web.cherokee.general/8833 <pre>Hi, I want to make some changes in cherokee-admin launcher to accept a user-defined password at command line (rather than automatically generate a random password). But I don't known how the sources are structured. Can someone tell me what file (or files) I need to change to do this? Is this https://github.com/cherokee/webserver/blob/master/cherokee/main_admin.c ? Thanks, -- Daniel Loureiro ------------------------------ _______________________________________________ Cherokee mailing list Cherokee&lt; at &gt;lists.octality.com http://lists.octality.com/listinfo/cherokee </pre> Daniel Loureiro 2013-04-17T09:13:34 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.web.cherokee.general