2013-07-02, 05:58:19
So I was trying to install GS on my webhost and I kept getting 403 errors. I opened a ticket with my webhost and they said that install.php was trying to call '/'.
At first, blocking '/' seemed pretty crazy. But they explained that the security restriction was aimed at blocking attacks against *NIX systems to the root file system (i.e. root file system that contains /etc, /sbin, etc.)
They weren't sure about the line number in install.php that was throwing the error but based on the logs, they determined this was the issue.
Is install.php necessary for proper installation? I see it does some preliminary checks and redirects to setup.php but I'm not sure whether it does anything vital to for the health of a GS system.
(If it doesn't do anything critical, I may just go to setup.php and just install GS.)
If it is necessary, is there a way to reformat the request (e.g. caling the full URL instead of '/') so my webhost doesn't throw a hissy fit?
Thank you all.
At first, blocking '/' seemed pretty crazy. But they explained that the security restriction was aimed at blocking attacks against *NIX systems to the root file system (i.e. root file system that contains /etc, /sbin, etc.)
They weren't sure about the line number in install.php that was throwing the error but based on the logs, they determined this was the issue.
Is install.php necessary for proper installation? I see it does some preliminary checks and redirects to setup.php but I'm not sure whether it does anything vital to for the health of a GS system.
(If it doesn't do anything critical, I may just go to setup.php and just install GS.)
If it is necessary, is there a way to reformat the request (e.g. caling the full URL instead of '/') so my webhost doesn't throw a hissy fit?
Thank you all.