I have a Piwik install sitting behind a varnish-caching server. My problem is varnish is by default caching responses to my API calls. Unfortunately, I don't have direct access to the varnish server, so I need to send the
"Cache-Control: no-cache"
header with my API responses. Is there a setting or a way to modify my piwik install to accomplish this? Thanks!
Add to .htaccess in your piwik install, core/API/ folder:
<Files Request.php>
Header set Cache-Control "no-cache"
</Files>
If you need to add the header to other URLs, follow the same pattern.
Note that Piwik already adds Cache-Control: max-age=0 to these responses, so if that's not working for you on the Request.php path you probably want to add this to .htaccess in the folder with piwik.js (root of piwik install) as well:
<Files piwik.php>
Header set Cache-Control "no-cache"
</Files>
Related
My WordPress website on a subdomain [ collective.terakaia.com ] has recently stopped loading font assets with the following errors in the console. Apologies in advance as I know there are several existing threads regarding the CORS policy issue. I just haven't been able to get any of them to work for my particular situation.
Console Errors:
Access to font at 'https://secureservercdn.net/198.71.233.51/e9h.41e.myftpupload.com/wp-content/themes/gridlove/assets/fonts/raleway-semibold-webfont.ttf' from origin 'https://collective.terakaia.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
I've attempted a few modifications to the .htaccess with no success. Here is the current .htaccess file code:
<ifmodule mod_headers.c="">
SetEnvIf Origin "^(.*\.terakaia\.com)$" ORIGIN_SUB_DOMAIN=$1
Header set Access-Control-Allow-Origin "%{ORIGIN_SUB_DOMAIN}e" env=ORIGIN_SUB_DOMAIN
Header set Access-Control-Allow-Methods: "*"
Header set Access-Control-Allow-Headers: "Origin, X-Requested-With, Content-Type, Accept, Authorization"
</ifmodule>
It's very possible that this is just a simple syntax error that I'm just not aware of. I don't have much experience dealing with this kind of issue.
Any help is appreciated, thank you!
Looks like the most recent update of Chrome solves the issue.
Using Netlify, can I add custom HTTP headers to a path on one domain but not another?
e.g. if I wanted my-domain.com to return a 301 with headers different to the headers returned by www.my-domain.com.
#talves has explained below why my initial approach (quoted) won’t work.
Given the below in netlify.toml, I expect to see my custom
Cache-Control header (and NOT see the Link header) when I run
curl -I http://hello-yoga.co.uk but that's not happening.
What am I doing wrong?
[[headers]]
for = "/"
[headers.values]
Link = "</yoga-people.svg>; rel=preload; as=image"
[[redirects]]
from = "http://hello-yoga.co.uk/*"
to = "https://www.hello-yoga.co.uk/:splat"
status = 301
force = true
headers = {Cache-Control = "public, max-age=2592000"}
Result:
$ curl -I http://hello-yoga.co.uk
HTTP/1.1 301 Moved Permanently
Cache-Control: public, max-age=0, must-revalidate
Link: </yoga-people.svg>; rel=preload; as=image
Location: https://www.hello-yoga.co.uk/
The headers in the redirect are added request headers sent to the redirect proxy (CUSTOM HEADERS IN PROXY REDIRECTS)
These allow you to pass custom headers added to the redirect request that for example could help identify your request. These are not response headers that get passed through. Use [[headers]] for that purpose as you show for the Link.
Netlify support confirmed the only way to do this is with two Netlify apps:
For the www subdomain
For the apex/root domain
Note: I am using Wordpress and serving the media files, css, js, etc. through Amazon CloudFront/S3.
Hello,
I know there are a lot of posts like this but I am still struggling. I was able to fix this issue for a majority of the font files that I am loading, however, this one continues to be an issue.
Access to Font at 'http://mycloudfrontID.cloudfront.net/wp-content/themes/bridge/css/font-awesome/fonts/fontawesome-webfont.woff2?v=4.6.3' from origin 'http://mydomainname' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://maxmajor.net' is therefore not allowed access.
The other font files are fine after I added this to my CORS policy on AWS S3:
<?xml version="1.0" encoding="UTF-8"?>
<CORSConfiguration xmlns="http://s3.amazonaws.com/doc/2006-03-01/">
<CORSRule>
<AllowedOrigin>*</AllowedOrigin>
<AllowedMethod>GET</AllowedMethod>
<MaxAgeSeconds>3000</MaxAgeSeconds>
<AllowedHeader>Authorization</AllowedHeader>
</CORSRule>
</CORSConfiguration>
and this is in my .htaccess:
<FilesMatch "\.(ttf|ttc|otf|eot|woff|woff2|font.css)$">
<IfModule mod_headers.c>
Header set Access-Control-Allow-Origin "*"
</IfModule>
</FilesMatch>
Any ideas why this error is still firing?
Thanks,
Brian
Try to change:
Header set Access-Control-Allow-Origin "*"
with this:
Header add Access-Control-Allow-Origin "*"
Also I read
How does Access-Control-Allow-Origin header work?
Font from origin has been blocked from loading by Cross-Origin Resource Sharing policy
that for security reasons you have to include your URL.
So, your .htaccess should have this:
<FilesMatch "\.(ttf|ttc|otf|eot|woff|woff2|font.css)$">
<IfModule mod_headers.c>
Header add Access-Control-Allow-Origin "http://mysitename.com"
</IfModule>
</FilesMatch>
Works for me!
Have you considered referring the following thread?
CORS Issue with woff2 fonts behind CDN in Chrome
It says
Turns out that the problem was actually with the Content-Type. As soon as I changed the content type to application/font-woff2 and invalidated the cache of these woff2 files, everything went through smoothly.
Are you sure that you are sending Authorization headers with your GET requests for the fonts?
If not, in your S3 CORS policy change
<AllowedHeader>Authorization</AllowedHeader>
to
<AllowedHeader>*</AllowedHeader>.
This tiny miss had bugged me for a month.
How can I insert a Cache-Control: no-transform HTTP header in a WordPress site without using a plugin? Can it can be inserted in .htaccess or function.php?
You should be able to add the Cache-Control header with .htaccess, if it's being served with Apache and you have .htaccess enabled:
Header set Cache-Control "no-transform"
I've read almost every post on stackoverflow in regards to CORS and whatever I try does not work. Here is my setup:
Ubuntu (digital ocean)
nginx
cdn: cdn77.com (not amazon)
cloudflare
wordpress with wp fastest cache
Each time a new setting was done I've purged cloudflare and restarted nginx.
This is what I've tried:
.htaccess (doesn't work)
<IfModule mod_headers.c>
<FilesMatch "\.(ttf|ttc|otf|eot|woff|font.css|css)$">
Header set Access-Control-Allow-Origin "*"
Header set Access-Control-Allow-Headers "Cache-Control, Pragma, Origin, Authorization, Content-Type, X-Requested-With"
Header set Access-Control-Allow-Methods "GET, PUT, POST"
</FilesMatch>
</IfModule>
nginx (doesn't work)
add_header Access-Control-Allow-Headers "X-Requested-With";
add_header Access-Control-Allow-Methods "GET, HEAD, OPTIONS";
add_header Access-Control-Allow-Origin "*";
I am pulling my hair out trying to figure out why font awesome wont show its icons on my site which is on a different domain.
.htaccess files are apache only, it will never work for Nginx.
With nginx it should work if theses headers are added to the font HTTP response... but it seems you do not own the fonts and you take the fonts from another website. The CORS headers need to be set by this website, not yours. Check what are theses headers on the fonts, and check that your website is allowed to use the fonts from there (else you will have to download the fonts on your website and add the headers on an nginx location based on the font extension.
I guess you confuse CORS headers and CSP headers (**C**ontent **S**ecurity **P**olicy). Where you can give a list of allowed resources for your website.