A minor problem is the added backslash (instead of index.php?site=thread i now get index.php?site=/thread) How could I change that?
But my much bigger problem is the way Froxlor manages it's vHost configs. Maybe I just don't get it!
Froxlor automatically creates a vHost file for every domain which already contains a rewrite:
location @rewrites {
rewrite ^ /index.php last;
}
My problem is that if I enter the code I would like to work into the domain's vHost entry in the Froxlor panel, the rule gets added AFTER the standard rewrite is done, therefore making my rule obsolete:
Question
bax
Hi!
I set up Froxlor on a Debian Wheezy with NGINX and PHP-FPM.
I'm trying to run a site which previously was running on an apache server with the following rewrite rules:
I thought about accomplishing the same on NGINX with the following:
A minor problem is the added backslash (instead of index.php?site=thread i now get index.php?site=/thread) How could I change that?
But my much bigger problem is the way Froxlor manages it's vHost configs. Maybe I just don't get it!
Froxlor automatically creates a vHost file for every domain which already contains a rewrite:
My problem is that if I enter the code I would like to work into the domain's vHost entry in the Froxlor panel, the rule gets added AFTER the standard rewrite is done, therefore making my rule obsolete:
Is there any way to make my rule work using Froxlor's vHost management?
Can I somehow change the default rewrite or prioritize mine?
There must be a way without changing Froxlor's Cronjobs!
I guess there are many people needing this.
Thank you already!
Link to comment
Share on other sites
5 answers to this question
Recommended Posts
Archived
This topic is now archived and is closed to further replies.