htaccess files exist in other directories and are not hidden.
Looks like I will have to allow overides in httpd.conf in addition to vhost.conf
htaccess files exist in other directories and are not hidden.
Looks like I will have to allow overides in httpd.conf in addition to vhost.conf
That won't solve your problem.
Is there a reason that you failed to confirm whether /includes/.htaccess exists or not?
Also, I find it a bit disconcerting that you state that *other* .htacess files exist but they are not hidden because the "." in the filename is the *nix standard that defines a "hidden" file.
I'm seeking a solution to your problem. You appear to be defensive to my approach, so just two questions before moving on.
1. Does the file /includes/.htaccess on your server?
2. What are the permissions for this file (should be 644).
Cheers
RodG
First sentence in my previous post answered the question that you said I didnt answer.
You didnt ask for the permissions originally, but yes they are all 644
When I say they are not hidden, I mean they are visable in my directory structure. Not using anything other than pure apache.
Last edited by pixelpadre; 18 Jun 2017 at 12:10 AM.
Hmmm, well no you didn't, and still haven't. It may have been implied as part of the "other directories" but I'm not willing to make that assumption. Historically I've wasted many hours going around in circles due to this kind of thing. Seriously, the .htaccess files in "other" directories are unimportant to the problem. The only important one is the one in the /includes/ folder and I really didnt think it too much to ask that you verify/confirm that this specific one exists.
No, I didnt ask previously which is why I asked this time. Could you please confirm that you actually checked that permissions are 644 and that this wasnt from memory or possibly you just said it was 644 because that is what I said it should be?
Im not sure what you mean about "pure apache", and "hidden" in this context does not mean they can't be seen in the directories. All files in all directories can be seen, even the hidden ones.
Anyway, lets try to move forward eh?
So, the file /includes/.htaccess exists, and it has permissions of 644 .... Next step is to set the permissions to 666 (temporarily) and edit the file by adding the words "hello world" right at the beginning of the file. save it.
Now point your webbrowser to yourstore.com/includes/
One of three things will happen. When you tell me the results that you are getting I will either be able to give a diagnosis, or will I be able to provide you with the next diagnostic step(s).
Cheers
RodG
internal server error 500 page
That's exactly what we want :)
What this is telling is us is that
1) Your allowoverrides are OK
2) The .htaccess file is in the correct location for purpose.
3) The .htaccess file is *currently* readable by the server process.
4) The .htaccess file is correctly named (Yes, I have seen cases where folk have renamed it for whatever reason and then wonder why it isn't working)
Next step. Same as b4, but leave the file permissions at 644. You should get the same 500 server error, so assuming you do - you should now remove the 'hello world' and resave the file.
FYI, The 'hello world' itself isn't important, pretty much any text that isn't recognized as valid syntax will cause the server 500 error. This is just a handy/useful trick/tip that will determine that the .htaccess file of interest is actually being used or not. If anything was amiss with those 4 points above, the file would be skipped and you'd be getting something *other* than the 500 server error.
So, now we know that all is good as far as finding and reading the .htaccess file you should now once again point your browser to
yourstore.com/includes/
While you are at it, also point it to
yourstore.com/includes/spiders.txt
If the *contents* of this .htaccess file are all correct, you *should* be greeted with a 'Forbidden' message for *both* tests. This is actually the response that the ZC installer is looking for - but since the problem you are having is failing this test that would imply that there is something not quite right with the contents of this file. This is what you'll need to investigate to seek a solution since all(?) other possibilities have been eliminated.
However, if you ARE getting all the expected results here - the plot thickens - We will no longer be looking at 'your' side of things - It means that for some reason or other the ZC installer is actually giving you a false report - I would even go as far to say just ignore it - The important thing at this stage is that *you* get the forbidden message when you point your browser to /includes/ and /includes/spiders.txt - After all, it is this that the ZC installer is testing for and if the installer is giving a false error report (which is where this is now headed) then there doesn't seem like there is anything that you can do to fix it anyway. Basically 'not your problem'
Cheers
Rod.
ps. I chose to use spiders.txt, the zc installer uses one of the .php files in the same folder. Both should be 'forbidden'
Last edited by RodG; 19 Jun 2017 at 05:08 AM.
We troubleshoot in the same methodical manner, very logical!
ok got the Forbidden error in both cases with 644
Feels like something unique to this server; others aren't complaining about it. I can't trigger it on my test servers that have a standard apache install and configured per our very basic guidelines.
Here's the code. I suggest you add some debug output to determine what response code you're getting and why.
https://github.com/zencart/zencart/b...ecker.php#L331
.
Zen Cart - putting the dream of business ownership within reach of anyone!
Donate to: DrByte directly or to the Zen Cart team as a whole
Remember: Any code suggestions you see here are merely suggestions. You assume full responsibility for your use of any such suggestions, including any impact ANY alterations you make to your site may have on your PCI compliance.
Furthermore, any advice you see here about PCI matters is merely an opinion, and should not be relied upon as "official". Official PCI information should be obtained from the PCI Security Council directly or from one of their authorized Assessors.