IE8 causes 404 errors when using Frontend 3.0
See original GitHub issueWe recently upgraded our app to Frontend 3.0.
As a result we have noticed that we are getting lots of 404 errors in our server logs from IE8 users requesting invalid URLs e.g. https://gateway.prod.nomis-api.service.hmpps.dsd.io:443/auth/fonts/bold-b542beb274-v2.woff2)%20format(%22woff2%22),%20url(/auth/fonts/bold-affa96571d-v2.woff)%20format(%22woff%22
It looks like IE8 doesn’t understand the @font-face
directive and treats format("woff2"),url(
as part of the URL too.
As a side issue woff2 isn’t supported in IE8 so shouldn’t be included in the IE8 css (https://github.com/alphagov/govuk-frontend/blob/master/dist/govuk-frontend-ie8-3.1.0.min.css).
Issue Analytics
- State:
- Created 4 years ago
- Comments:9 (9 by maintainers)
Top Results From Across the Web
I'm getting a 404 error on a page that does exist
We usually get the error 404 "Page not found" whenever someone asks for a page that's simply not available on your site. The...
Read more >ACF FrontEnd 3.x + Events Manager = bug leading to error 404
it seems that ACF Frontend (from v3.0.5) is having a conflict with Events Manager, leading to error 404 whatever the redirection is made...
Read more >Net Core deployed app throws error 404 on IIS - Stack Overflow
I'm working on a web app with Angular 7 as Front End and Net Core 3.0 as Back End. Everything works fine in...
Read more >How To Fix Error 404 Page Not Found In WordPress?
Because this error discloses inconsistency with a link, it can typically resolve the same by properly configuring and saving WordPress ...
Read more >Roundcube Community Forum
MobileCube 3.0/3.1 404 Error with Internet Explorer. ... I've tried IE8 and IE9 on multiple PCs with the same results.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Yeah I think anything like that would fall some way outside our support matrix
I did some investigation. The font paths themselves could be naively fixed by adding
?#iefix
to the end of the URLs which is what we used to do in v2. However this would just mean that the woff2 files get downloaded by IE8 which is redundant as IE8 doesn’t support the format.We could put a
govuk-if-ie8
check in font-faces which would stop them being outputted for IE8. This would mean that the font files aren’t downloaded by IE8 and we fall back to Arial. This could be an okay fix? However it would mean that CSS for IE8 would still say:font-family: "GDS Transport", Arial, sans-serif;
which is somewhat confusing but then this is what v3 already does anyway.Or we could define a font family for IE8.
(we don’t have access to
govuk-if-ie8
mixin in/settings
).Thoughts? I’ll pick this up later.