Deny from all is an .htaccess command (the actual content of that file you are trying to view). Not a denial of being able to edit the file. Just reopen the .htaccess file in the text viewer of choice and make the alterations as you so desire, save it, then reupload it to your folder … Read more
www to non www with https RewriteEngine on RewriteCond %{HTTP_HOST} ^www\.(.*)$ [NC] RewriteRule ^(.*)$ https://%1/$1 [R=301,L] RewriteCond %{ENV:HTTPS} !on RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [R=301,L]
I guess it’s meant that you enable gzip compression for your css and js files, because that will enable the client to receive both gzip-encoded content and a plain content. This is how to do it in apache2: <IfModule mod_deflate.c> #The following line is enough for .js and .css AddOutputFilter DEFLATE js css #The following … Read more
You can force browsers to cache something, but You can’t force browsers to clear their cache. Thus the only (AMAIK) way is to use a new URL for your resources. Something like versioning.
.htaccess flag list C (chained with next rule) CO=cookie (set specified cookie) E=var:value (set environment variable var to value) F (forbidden – sends a 403 header to the user) G (gone – no longer exists) H=handler (set handler) L (last – stop processing rules) Last rule: instructs the server to stop rewriting after the preceding … Read more
the Header directive is in the mod_headers apache module. You need to make sure that module is loaded into the apache server.
This should work: Header add Access-Control-Allow-Origin “*” Header add Access-Control-Allow-Headers “origin, x-requested-with, content-type” Header add Access-Control-Allow-Methods “PUT, GET, POST, DELETE, OPTIONS”
You need to create a new .htaccess file in the required directory and include the Satisfy any directive in it like so, for up to Apache 2.3: # allows any user to see this directory Satisfy Any The syntax changed in Apache 2.4, this has the same effect: Require all granted
Not the place to give a complete tutorial, but here it is in short; RewriteCond basically means “execute the next RewriteRule only if this is true”. The !-l path is the condition that the request is not for a link (! means not, -l means link) The RewriteRule basically means that if the request is … Read more
I had this problem too. My advice is look in your server error log file. For me, it was that the top directory for the project was not readable. The error log clearly stated this. A simple sudo chmod 755 <site_top_folder> fixed it for me.