Before attempting to upgrade my existing 155a store to 156, I have a demo version of the default 155a installed, that I am trying the upgrade process on.

When running the zc_install script, it is warning me that "Support for ".htaccess" files is not enabled."

Clicking on this error shows (in part) the following information:

Possible causes:

You may not be using Apache as your Web Server (".htaccess" files are unique to the Apache Web Server), or,
Support for ".htaccess" is disabled or misconfigured, or,
The ".htaccess" files that come with Zen Cart have not been uploaded to your site.
Files starting with ".", such as ".htaccess" files, are usually treated as "hidden" files and your FTP program may have failed to upload these if you have turned off the display and/or transfer of such hidden files in its settings.

However,

1. my ISP is using Apache; Easy Apache 4 I believe.
2. support for .htaccess is NOT disabled; I use and am using .htaccess files in many places successfully.
3. The .htaccess file in the includes folder has been uploaded.

Any reason why this warning would be showing in light of the above? Is there any way to "test" whether the .htaccess file is blocking what it is supposed to be blocking?

That message appears when zc_install does a test to see if .htaccess rules are properly blocking access to files that nobody has any business accessing from a browser.

You can simulate the very same test by going to: http:// your_site.com/includes/filenames.php
It's expecting a 403 Forbidden response.

Thanks. I meant to say I was upgrading 155f to 156a.

I went ahead and did the upgrade and it completed successfully.

By running the test, I am indeed getting a 403 error page. So it would seem that the upgrader is incorrectly reporting this warning, possibly.

karma-lab:

By running the test, I am indeed getting a 403 error page. So it would seem that the upgrader is incorrectly reporting this warning, possibly.
Maybe. It's not intended to be perfect. It's limited in what it can do, since it's simulating a visit, but coming from the same server as the site it's testing ... which may influence the results in some cases depending on server configuration. It can't catch every situation, but it's intended to make you investigate ... so it's doing its job at least ;)

Thanks. How true. ;)

But might I suggest that you include the directions for performing this test in the further information that comes up when you click on this warning?

Something like:

This test/analysis is not 100% conclusive. If you believe that your .htaccess support is correctly configured, after the upgrade you can test it by attempting to load the following URLS. blah-blah etc.

That might avoid questions like this in the future. Just a suggestion.

Revisiting due to .htaccess error loading trial 1.5.7

When I try the "filenames.php" test, I get status "301 Moved Permanently", which redirects to a page "403.shtml", which itself returns status "404 Not Found"

Maybe some of this info will help```
===[root@host 1102428]# curl -ILs http://test.netzencommerce.com/includes/filenames.php
HTTP/1.1 301 Moved Permanently
Date: Mon, 13 Apr 2020 20:35:51 GMT
Server: Apache
Location: https://test.netzencommerce.com/403.shtml
Content-Type: text/html; charset=iso-8859-1

HTTP/1.1 404 Not Found
Date: Mon, 13 Apr 2020 20:35:51 GMT
Server: Apache
Content-Type: text/html; charset=iso-8859-1

Can you describe the environment and symptoms?

• You are installing on what platform?
• You try to do a zc_install and get blocked?

OK I see - you get that message on the zc_install screen.

Let me look at that but please keep going. Run zc_install and install.

I'm getting myself in trouble again using "error"

This is the same notice received by the OP, discussed in the closed item I commented on earlier, and information as to how our Apache servers are responding to the test offered by DrByte.

Please make the following edit:
zc_install/includes/classes/class.systemChecker.php line 347
change 'http://'
to 'https://'

(just add the "s")

and then retry.

That worked which leads me to believe we have more of a problem.

With it set to https, the folks without an SSL will get an error and with it left to http, the folks WITH SSL will get an error. It won't work with just // as some links will.

Do you gather the same from the results?

Don't worry - this issue will be fixed before the release. Thank you for your help in testing.

Please proceed - let's see what else you can find!

If you have time, it would be a big help for you to pull the file out of

https://github.com/zencart/zencart/pull/3249

and try this test again. Should work for both http:// and https:// environments.

dbltoe:

Revisiting due to .htaccess error loading trial 1.5.7

When I try the "filenames.php" test, I get status "301 Moved Permanently", which redirects to a page "403.shtml", which itself returns status "404 Not Found"

Maybe some of this info will help```
===[root@host 1102428]# curl -ILs http://test.netzencommerce.com/includes/filenames.php
HTTP/1.1 301 Moved Permanently
Date: Mon, 13 Apr 2020 20:35:51 GMT
Server: Apache
Location: https://test.netzencommerce.com/403.shtml
Content-Type: text/html; charset=iso-8859-1

HTTP/1.1 404 Not Found
Date: Mon, 13 Apr 2020 20:35:51 GMT
Server: Apache
Content-Type: text/html; charset=iso-8859-1

You'll notice that zc_install is indeed following the server's redirect. 
So, why not fix the server's broken redirect instead of having the server return a 404-not-found?
Zen Cart shouldn't have to magically figure out why your server is giving an incorrect response.