Jump to content
thirty bees forum
  • 0

Nginx friendly URLs


TobyMudito

Question

According to the software specifications, you can use Nginx as server.

But, if you want to activate the URL friendly option in the SEO & URLs tab, you see the following message: 1. Create a blank .htaccess file 2. Give it write permissions.

I have tried to activate it, but it shows the written message.

I don't want to use Apache as a server, since I consider Nginx a better server. So, What is the action to perform to fix this problem?

Thank you!!

Link to comment
Share on other sites

22 answers to this question

Recommended Posts

  • 0

Thank you. I just have created the empty .htaccess file that the page tells me, and everything worked fine. It would be great if a better description will appear just to clarify that is necessary to create the file even if you are using nginx.

By the way. The nginx configuration is the same as Prestashop uses, so, for those who want to use Nginx, you just have to use the same configuration.

Thank you and regards!! :dancers:

Link to comment
Share on other sites

  • 0

Ahh okay - hopefully one day TB is possible to figure out if it should serve webp or jpg, depending on the users browser/platform.

i would ad following to the nginx config, from my experience a few modules needs this rewrite.

rewrite "^/module/([a-zA-Z0-9-]*)/([a-zA-Z0-9-]*)$" /index.php?fc=module&module=$1&controller=$2 last;

Link to comment
Share on other sites

  • 0

just found a small article in my bookmarks i played with.

https://github.com/uhop/grunt-tight-sprite/wiki/Recipe:-serve-WebP-with-nginx-conditionally

had the other pice of code in a dir with different nginx config options.

Dont think there is 100% perfect solution since you have to check if there http_accept allows webp to be served.

Link to comment
Share on other sites

  • 0

If we did fit in the Recipe for WebP Nginx in to the base config file for TB documentation.

And added the htaccess counter part to the .htaccess file.

Then it should be possible to add webp image generation for TB, hopefully with a ajax driven image regeneration so we avoid the time outs that can give.

Link to comment
Share on other sites

  • 0

It's in the nature of HTTP that one can't push anything. One can only declare files as short lived, in the hope that the browser requests them again. Alternatively one can change the file name, so the next page request makes the browser requesting that other file. Third strategy is to deliver some JavaScript which repeatedly requests the same file.

Which raises the question: why do you feel a need for "pushing" CSS? Each of the strategies mentioned makes caching pretty pointless.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...