Anyone could help me with this .htaccess file?
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
I'm trying to use my custom permalinks in Wordpress and I need to
"emulate" this behaviour in Cherokee.
Thanks in advance!.
--
Saludos:
Antonio Pérez
ATENCIÓN: Antes de imprimir este mensaje valora si verdaderamente es necesario.
De esta forma contribuimos a la preservación del Medio Ambiente.
_______________________________________________
Cherokee mailing list
Cher...@lists.octality.com
http://lists.octality.com/listinfo/cherokee
Miguel Ángel
El 05/09/2008, a las 19:00, "Antonio Pérez" <apli...@skarcha.com>
escribió:
> I need it too :) I still have it on my pending tasks ':)
Guys, I'm pretty sure you are gonna love the new 'wizards' feature
shipped with the upcoming Cherokee 0.9 :-)
> El 05/09/2008, a las 19:00, "Antonio Pérez" <apli...@skarcha.com>
> escribió:
>
>> Hi!
>>
>> Anyone could help me with this .htaccess file?
>>
>> <IfModule mod_rewrite.c>
>> RewriteEngine On
>> RewriteBase /
>> RewriteCond %{REQUEST_FILENAME} !-f
>> RewriteCond %{REQUEST_FILENAME} !-d
>> RewriteRule . /index.php [L]
>> </IfModule>
>>
>> I'm trying to use my custom permalinks in Wordpress and I need to
>> "emulate" this behaviour in Cherokee.
This is something you can configure with the "Behavior" section of your
Virtual Server.
It first look, I'd say that something like this could be enough:
- Extension php "FastCGI"
- Directory /images "Static content"
- Directory /bla, bla "Static content"
- Directory /lalala "Static content"
- Default ^.+$ "Redirection" (to /index.php?$1)
Good luck!
--
Greetings, alo
http://www.alobbs.com/
>> I need it too :) I still have it on my pending tasks ':)
>
> Guys, I'm pretty sure you are gonna love the new 'wizards' feature shipped
> with the upcoming Cherokee 0.9 :-)
I hope!, I hope!... :D
>>> I'm trying to use my custom permalinks in Wordpress and I need to
>>> "emulate" this behaviour in Cherokee.
>
> This is something you can configure with the "Behavior" section of your
> Virtual Server.
>
> It first look, I'd say that something like this could be enough:
>
> - Extension php "FastCGI"
> - Directory /images "Static content"
> - Directory /bla, bla "Static content"
> - Directory /lalala "Static content"
> - Default ^.+$ "Redirection" (to /index.php?$1)
Ufff!
But this need to add rules every time I create a new directory, or file in "/".
I think the problem here is how to get those rewrite conditions works
on Cherokee.
> Good luck!
Anyway, it's a good hack at the moment... Thanks for your help. ;)
--
Saludos:
Antonio Pérez
ATENCIÓN: Antes de imprimir este mensaje valora si verdaderamente es necesario.
De esta forma contribuimos a la preservación del Medio Ambiente.
> - Extension php "FastCGI"
> - Directory /images "Static content"
> - Directory /bla, bla "Static content"
> - Directory /lalala "Static content"
> - Default ^.+$ "Redirection" (to /index.php?$1)
First problem... WordPress use PATH_INFO, so redirection must be:
"/index.php$1", and Cherokee doesn't recognize it as an .php extension
file, so it enters in a loop.
--
Saludos:
Antonio Pérez
ATENCIÓN: Antes de imprimir este mensaje valora si verdaderamente es necesario.
De esta forma contribuimos a la preservación del Medio Ambiente.
I think that some rewrite rules could be only translates if we
get those kind of conditionals: "-f" it's not a file, and "-d" it's
not a directory . Other way could be putting the static files as first
rules and leting it fallback on the rewrite when the file doesn't exist.
Miguel Ángel
El 05/09/2008, a las 20:22, "Antonio Pérez" <apli...@skarcha.com>
escribió:
No. That means that you would have to add a new rule whenever you create
a new directory *within your blog directory* (or virtual server).. which
should be certainly something very unusual.
> I think the problem here is how to get those rewrite conditions works
> on Cherokee.
That is not going to happen unless a really good reason comes up. That
is one of those approaches that makes web servers run so slow.
I don't think that you will have to add more of three of four rules to
configure the whole Wordpress thing, so assuming a performance penalty
for saving a couple of rules does not really make sense to me.
Think of it in this way: You spend 15 secs adding the rule, and your
server will run faster during the next N years. It does sound like a
good time inversion, doesn't it?
>> Good luck!
>
> Anyway, it's a good hack at the moment... Thanks for your help. ;)
Independently of whether we could kind of hide it behind a wizard, it is
the way it has been designed to work. There is neither 'hacks' or
'work-arounds' involved on this.
Keep in mind that there are alternative ways of doing things. It does
not matter whether any other web server works in the same way or not.
We are making independent decisions, and that is one of the reasons why
Cherokee is currently outperforming all the rest.
--
Greetings, alo
http://www.alobbs.com/
It depends on your configuration whether Cherokee detects the php
extension or not.
Anyway, a few days ago Rui found a bug that might be hitting you with
this. It's related to how the PATH_INFO string is generated. I will get
back to you guys as soon as I fix it on Trunk (hopefully within the next
few days).
--
Greetings, alo
http://www.alobbs.com/
>> But this need to add rules every time I create a new directory, or file in
>> "/".
>
> No. That means that you would have to add a new rule whenever you create a
> new directory *within your blog directory* (or virtual server).. which
> should be certainly something very unusual.
Ok... it's true.
>> I think the problem here is how to get those rewrite conditions works
>> on Cherokee.
>
> That is not going to happen unless a really good reason comes up. That is
> one of those approaches that makes web servers run so slow.
>
> I don't think that you will have to add more of three of four rules to
> configure the whole Wordpress thing, so assuming a performance penalty for
> saving a couple of rules does not really make sense to me.
>
> Think of it in this way: You spend 15 secs adding the rule, and your server
> will run faster during the next N years. It does sound like a good time
> inversion, doesn't it?
I had not thought in this way... You are right. :)
--
Saludos:
Antonio Pérez
ATENCIÓN: Antes de imprimir este mensaje valora si verdaderamente es necesario.
De esta forma contribuimos a la preservación del Medio Ambiente.
> I think that some rewrite rules could be only translates if we get
> those kind of conditionals: "-f" it's not a file, and "-d" it's not a
> directory . Other way could be putting the static files as first rules
> and leting it fallback on the rewrite when the file doesn't exist.
Yes, that is exactly the way it is supposed to be configured.
If you add a couple of additional rules (for the -f, -d cases) you will
point the server something that otherwise it would have to recheck
millions of times on execution.
Adding those rules, you are spending a little time for getting an
interesting performance improvement.
--
Greetings, alo
http://www.alobbs.com/
I'm trying to run it in a /blogs/ subfolder, not as a virtual server
in the root folder. Though I guess I could change that with some work.
Necesito ayuda! (I need help!)
On Sep 6 2008, 4:23 am, Miguel Ángel <miguelan...@ajo.es> wrote:
> Hi :)
> the problem on these rules, as antonio says, is that wordpress
> creates file irks dinamically. I'm not sure about worspress but that
> happened to me with wordpress mu.
>
> I think that some rewrite rules could be only translates if we
> get those kind of conditionals: "-f" it's not a file, and "-d" it's
> not a directory . Other way could be putting the static files as first
> rules and leting it fallback on the rewrite when the file doesn't exist.
>
> Miguel Ángel
>
> El 05/09/2008, a las 20:22, "Antonio Pérez" <aplis...@skarcha.com>
> Chero...@lists.octality.comhttp://lists.octality.com/listinfo/cherokee
Permalinks in Wordpress MU are set as the custom:
/index.php/%year%/%monthnum%/%postname%/
This worked, but it is complicated, and may be over-the-top (can't
remember too much)...
Behaviour Rules
1)
Complex: (Not (File Exists: Any file)) AND (Regular Expression:
^/([_0-9a-zA-Z-]+)/(wp-.*|.*\.php(\?.*|))$)
Handler Internal Redirection: ^/([_0-9a-zA-Z-]+)/(wp-.*)$ to
^/([_0-9a-zA-Z-]+/)/(.*\.php(\?.*|))$
Handler Internal Redirection: ^/([_0-9a-zA-Z-]+/)/(.*\.php(\?.*|))$ to /$2
2)
Regular Expression: ^(.*)\.php(\?.*|)$
Handler: FastCGI
3)
Complex: Not (File Exists: Any file)
Handler Internal Redirection: ^/(.*)$ to /index.php
3)
Default, List & Send
If you'd prefer me to take screenshots of the behaviour settings, then
just let me know :P
Cheers,
Matt.
2009/8/27 Urko Masse <urko....@gmail.com>
You'll still want to reference my previous email, as some of the
regular expressions are cut short in the screenshots as they are
longer than the input text box.
Cheers,
Matt.
I'm glad you got it sorted. I don't think I ever got as far as
uploading images when I installed it as a quick test!
Let me know if there is anything else I can help with though.
Cheers,
Matt.