Sorry, but you do not have the capability to view this topic
-
- Topics: 1
- Replies: 2
- Total posts: 3
Post count: 2I’m seeing some stranger behavior from the FontAwesome directory. This is causing 404 errors which I would like to prevent at all cost.
From the access logs:
1. [09/Feb/2016:12:39:36 -0700] “GET /fonts/fontawesome-webfont.woff2?v=4.3.0 HTTP/1.1” 404 14186
2. [09/Feb/2016:12:39:38 -0700] “GET /fonts/fontawesome-webfont.woff?v=4.3.0 HTTP/1.1” 404 14186
3. [09/Feb/2016:12:39:40 -0700] “GET /fonts/fontawesome-webfont.ttf?v=4.3.0 HTTP/1.1” 404 14186
4. [09/Feb/2016:12:39:42 -0700] “GET /wp-content/themes/layers-hostme/assets/css/fontawesome/fonts/fontawesome-webfont.woff2?v=4.3.0 HTTP/1.1” 304NOTE: fontawesome-webfont.woff2 404’s, but then a couple seconds later return a 304 Not Modified, but with a different path.
[09/Feb/2016:12:22:08 -0700] “GET /fonts/fontawesome-webfont.woff2?v=4.3.0 HTTP/1.1” 404
[09/Feb/2016:12:22:10 -0700] “GET /fonts/fontawesome-webfont.woff?v=4.3.0 HTTP/1.1” 404
[09/Feb/2016:12:22:12 -0700] “GET /fonts/fontawesome-webfont.ttf?v=4.3.0 HTTP/1.1” 404 1
[09/Feb/2016:12:22:13 -0700] “GET /wp-content/themes/layers-hostme/assets/css/fontawesome/fonts/fontawesome-webfont.woff2?v=4.3.0 HTTP/1.1” 200 57087 “http://www.vm3enviro.com/wp-content/themes/layers-hostme/assets/css/fontawesome/css/font-awesome.css?ver=4.4.2” “Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/47.0.2526.111 Safari/537.36”NOTE: fontawesome-webfont.woff2 404’s, but then a couple seconds later return a 200 Success Referred from the main font-awesome.css file.
The only reference to “/fonts/fontawesome-webfont.EXTENSION” I can find in in font-awesome.css. Is it possible there’s another reference in a script somewhere?
My main question is how to prevent these 404’s from occurring?
Thanks!