Apache 2.4 mod_rewrite issues (on GoDaddy)

[Martimiz]

Hi,

It looks like something went wrong with a series of SilverStripe installs (2.4?) and mod_rewrite on goDaddy after a recent upgrade to Apache 2.4. Please read these forum posts:

http://www.silverstripe.org/general-questions/show/23917?start=16

A GoDaddy representative came up with a solution, by changing some code in main.php, and although I salute them for their efforts, I think this might possibly not be the right approach. I usually work with Lighttpd, so I'm not that into htaccess, but I think changes should be made there? Is this a general Apache 2.4 problem (so it might start effecting others too)? Can anyone possibly shine some light on this?

Just thought to mention :)

Martine

[g4b0]

I just upgraded to apache 2.4 and I'm having a similar issue: It seems that actual .htaccess is not working anymore, rewrite works fine for everything but the homepage, that is processed through index.php.

Does anybody have a working solution to this issue?

g4b0

[Lamin Barrow]

I got a similar issues recently for a client site. 

Anyways, delete or rename the index.php from your website root and see if it works.

[g4b0]

It works fine, but it's a workaround. I think it will be better to find a .htaccess solution, isn't it?

g4b0

[Giulio Bonanome]

Hi,

I've update my machine (Ubuntu 13.10) and found this Apache 2.4 issue. 

Anyone came up with a different solution? Is removing index.php the only workaround?

Thanks in advance for any help.

Giulio

[Daniel Hensby]

Really the index.php file is there just to provide a fallback for environments without rewrite support, so deleting the file isn't really a terrible thing to do as it should never be used if mod_rewrite is on.

I'm sure it would be possible to write a conditional in the mod_rewrite for empty URL to be handled by framework/main.php

[Zauberfisch]

this sounds like the perfect opportunity to do some refactoring on main.php and finally replace $_GET['URL']

--
You received this message because you are subscribed to the Google Groups "SilverStripe Core Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to silverstripe-d...@googlegroups.com.
To post to this group, send email to silverst...@googlegroups.com.
Visit this group at http://groups.google.com/group/silverstripe-dev.
For more options, visit https://groups.google.com/groups/opt_out.

[Giulio Bonanome]

Thanks for the answers (and +1 for refactoring).

After finding the correct documentation: http://httpd.apache.org/docs/2.4/mod/mod_dir.html#directoryindex I've found a new option for Apache: DirectoryIndex disabled

I've used it in my userdir module that now look like this

<Directory /home/*/public_html>

         AllowOverride All

         DirectoryIndex disabled

         Options MultiViews Indexes SymLinksIfOwnerMatch IncludesNoExec                

</Directory>

Also I must use "AllowOverride All" because Apache 2.4 has "None" set by default. Finally I can leave that index.php where it is, but the system work like before.

Cheers,

Giulio

[Cam Findlay]

I have found on the forums getting SS to work under Apache 2.4 raises this issue. I think I have answered a heap of posts pointing to the example here on the dev list.

What can be done to imporve this, is there something in SS core that can be altered to negate this issue or is it always going to be about the user setting up there apache rewriting as mentioned here?