Nginx equivalents for htaccess files

Need some feedback on this:

https://github.com/zencart/zencart/issues/667.

Also, not clear what the htpassword setup in the download folder does since "Require Valid User" is commented out.

Dayo:

Also, not clear what the htpassword setup in the download folder does since "Require Valid User" is commented out.
The .htnopasswd is just an empty placeholder. If the #Require valid-user is uncommented, then those AuthXXXX params will basically deny all access to that folder.

Zen Cart offers the storeowner multiple ways to serve downloadable resources. One way (and is a fallback if others don't work) is to serve the file directly from the /download folder. But this doesn't allow control over link-sharing or limiting number of times a download may be done.
Other ways are: redirected to a symlinked file dynamically created in the /pub folder (linked back to the source file in the /download folder); or streaming the file in-real-time.
The default enabled setting is to redirect to a symlink in the pub folder.

So, sometimes storeowners want to block any direct access of content in the /download folder.

Hi,

Sorry to bother you but can you respond to the CLA query at on Github so I know how to proceed?

Thanks

Replied to the CLA email address and sent a PR. Not sure whether the CLA was delivered though as I got an error message from the mail server.

Was wondering whether an automated tool such as clahub.com or cla-assistant.io would be a better approach.

Hmm ... the email address listed is used for dozens of other things too, and gets hundreds of messages daily.
Without knowing the error it's hard to know why it rejected yours.

And, yes, we've considered some automated tools, but none of them is ideal so it's been hard to settle on any one of them.

Been in the wastes of the Finnish Lapland for a while and only just seeing this on return to civilisation.

The error message received was:

Delivery to the following recipient failed permanently:

     ####@zencart.com

Technical details of permanent failure:
Google tried to deliver your message, but it was rejected by the server for the recipient domain zencart.com by zen-cart.com. [104.236.245.70].

On the automated tools, I thought they would just present the contributor with a license in a manner similar to the two tests currently done and then the team can decide whether to merge or not.

In any case, curious as to whether the test run you were going to do worked or not (bearing your workload in mind!).

When emailing you forgot the hyphen in the domain name zen-cart