Alvaro Lopez Ortega wrote: > Hello Pascal!
Hello Alvaro! Thank you for taking the time to reply -- I had totally not realized I had come to bother you right on release day. Sorry about the bad timing! > [KeepAlive option on virthosts] > That's a good point, actually. I have just logged it as a RFE: That's great, thanks! > A new rule type implementing this sort of checking arrived at trunk > yesterday. You can either wait a few weeks to get the new release, or > run trunk. Great! I pulled and compiled trunk to test it so as to give you feedback. See below. > If the file weren't exist, the rule wouldn't match, and the request > would be handled by another rule. In this case, the default Djando > rule (scgi/fastcgi) would likely be used. Okay, it might be I still need some explanations. I created a rule that tests whether the file 'index.html' exists, and associated it with a L&S handler. Underneath, I put a catch-all handler for Django. Now it displays the file if I go to http://localhost/index.html, which is correct, but if I go to http://localhost/ it goes to Django, even though I specified index.html as the directory index. What am I doing wrong? For that matter, is there a way to give the 'File exists' rule a wildcard to match against? Basically I would like it to: - Check whether the requested URL corresponds to a file (regardless of its name) in the document root, and if so, serve it; - Check whether the requested URL corresponds to a directory in the document root that contains an index file, and if so, serve that file; - Otherwise don't match and pass the request to the next handler. I'm sorry to bother you with this. :) I feel like I'm fumbling WAY more than I should. > - As long as cherokee-admin binds to lo, you cannot access it > remotely. Actually, on the virtual server I'm renting, you can, that's my problem. It's a quirk of the virtualisation technology they are using: there's no true loopback interface, so attempts to bind to 127.0.0.1 really bind to the *public* interface instead. But! I see that 0.10 implemented password protection for cherokee-admin, so as far as I'm concerned everything is now great. :) Thanks again for your reply and for the good work with Cherokee, -- P. _______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
