Moon
Moon copied to clipboard
Fix FontAwesome path
$fa-font-path ends has a trailing slash, which that browsers will do requests towards /assets/fonts/FontAwesome//fontawesome-webfont.{eot,woff,ttf} as per _sass/vendor/font-awesome/_path.scss .
For most of modern web servers it's fine, as they will flatten more than 1 forward slash to 1. That is: a//b -> a/b ... However this is not the case when hosting the page in a Amazon AWS S3 bucket, as it interprets it as a literal path that doesn't exist.
Removing the trailing slash from $fa-font-path solves the issue.
See: https://forums.aws.amazon.com/thread.jspa?threadID=13898