i'm a bit unsure how to approach this one..
I have a site hosted on BOA with some embedded webfonts that work fine on that domain, there's a central "webfont.css" file that has @font-face rules referencing other fonts on the same domain.
When I try to reference the same files from a different server (Amazon Cloud), with a different subdomain but on the same domain, Firebug reports "200 OK" responses from the site hosted by BOA but the file sent is empty.
everything is using https, with a valid wildcard certificate installed on both servers.
I assume that this is some security configuration set by BOA in nginx that I'm unaware of, which is why i'm posting here first.
Comments
Comment #1
thedavidmeister CreditAttribution: thedavidmeister commentedI managed to work around this by dropping the fonts on an Apache server with a valid SSL cert and drop the following into a .htaccess file:
how would i set up the equivalent in nginx so that site managed with Aegir will happily send out webfont files?
Comment #2
omega8cc CreditAttribution: omega8cc commentedThis is because we use
$host
in the rewrite to protect files from being requested from other (sub)domains, not defined as aliases.See the line http://drupalcode.org/project/barracuda.git/blob/HEAD:/aegir/conf/nginx_...
To override this, you need to use the extra config:
In the included config file, as explained in the how-to: http://drupalcode.org/project/barracuda.git/blob/HEAD:/docs/HINTS.txt#l16
Note: it will work only in Octopus instance. If you are using Barracuda instance, you need to figure out how to add this.
Comment #3
thedavidmeister CreditAttribution: thedavidmeister commentedwill running the octopus automated update script kill this if i overwrite it?
Comment #4
omega8cc CreditAttribution: omega8cc commentedNo, Octopus will not touch this extra config file, it will just include it as-is.
Upgrade overwrites only standard config files, by default installed and included in every vhost.
Comment #5
thedavidmeister CreditAttribution: thedavidmeister commentedawesome! thanks for that :) i'll try it out next week.
Comment #6
omega8cc CreditAttribution: omega8cc commented