[MGNLUI-4126] AdminCentral font disappears with IE11 over HTTPS if Pragma header present Created: 24/Jan/17  Updated: 13/Mar/17  Resolved: 09/Mar/17

Status: Closed
Project: Magnolia UI
Component/s: None
Affects Version/s: 5.5.1
Fix Version/s: None

Type: Bug Priority: Blocker
Reporter: Bence Vass Assignee: Maxime Michel
Resolution: Obsolete Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

IE11 or lower


Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:
Sprint: Basel 86
Story Points: 8

 Description   

At the moment Magnolia AdminCentral is not compatible with IE11 over https

How to reproduce with IE11 on https://demo.magnolia-cms.com:

  • Log in
  • Open Pages App
  • Edit a page (f.e. sportstation)
  • reload the page
  • watch the fonts and icons (which are part of MagnoliaIcons.woff) disappear

The trigger for this issue was a change in styles.css (for all fonts, not just MagnoliaIcons) done in MGNLUI-3983.

The reason for the issue is an IE bug with fonts over https, which apparently won't be fixed:
https://connect.microsoft.com/IE/feedbackdetail/view/992569/font-face-not-working-with-internet-explorer-and-http-header-pragma-no-cache

The only workaround at the moment is to remove the "pragma=no-cache" header from the response when loading WOFF files.



 Comments   
Comment by Federico Grilli [ 24/Jan/17 ]

Hello Bence, thank you for reporting this issue and providing a possible solution. We were actually able to reproduce it.

Federico, for the Magnolia team

Comment by Mikaël Geljić [ 03/Mar/17 ]

I investigated that few weeks back, but didn't quite wrap it up. Anyhow, my note appears in issue links by now. Two main suggestions:

  • Bypass the CacheFilter for /.magnolia/admincentral and /VAADIN altogether (currently merely UIDLs are bypassed)
    • Effectively leaving Vaadin to handle caching of the static resources it serves
  • Mid-term (follow-up in cache module), re-evaluate presence of the Pragma header in our default cache policies
    • see info.magnolia.module.cache.executor.SetExpirationHeaders
Comment by Maxime Michel [ 08/Mar/17 ]

I have made good progress as far as removing the Pragma header is concerned, however I'm currently unable to reproduce the problem, both with IE11 and IE9. I can only reproduce it with an IE9 VM at the following URL: https://font-face.korbball-ruswil.ch/pragma/Pragma.html

However, that page serves the HTML, WOFF and CSS with the Pragma header. A 5.5.2 bundle doesn't do that for the WOFF and CSS files. I have asked fgrilli to see if he can still reproduce the problem. If he can't, it means there is a change in the cache module that has fixed it.

Is it still a problem for you, bvass?

Comment by Federico Grilli [ 08/Mar/17 ]

Just tried to reproduce it on current demo (Magnolia EE 5.5.2, Windows7, IE11) and actually the issue seems to have gone.

Comment by Bence Vass [ 09/Mar/17 ]

Hi, in Magnolia 5.5.2 the issue is apparently solved. This is because you don't set the Pragma response header anymore, as suggested.

If you could point me to what has been changed to achieve this, that would be great.

Comment by Maxime Michel [ 09/Mar/17 ]

Thanks for your answer. We enabled caching again for AdminCentral with MGNLCACHE-164. We had previously removed it for 5.5.1 with MGNLCACHE-12.

Comment by Maxime Michel [ 09/Mar/17 ]

Closing as couldn't be reproduced with a current bundle neither by us nor by the reporter.

Comment by Mikaël Geljić [ 09/Mar/17 ]

Worth clarifying:

  • MGNLCACHE-12 disabled browser cache on author instances in 5.5.1. This was deemed too broad.
  • MGNLCACHE-164 (5.5.2) now only disables browser cache according to magnolia.develop property.

As such, I can't see how this would not affect a production author instance anymore?

Comment by Bence Vass [ 10/Mar/17 ]

I have the same suspicion, additionally this is also a problem for any public instances and websites that use woff (and other font) files.

This basically means that every customer has to build a custom solution to remove the pragma header (if he wants his page to be compatible with IE), because at the moment this behaviour is not configurable.

Comment by Maxime Michel [ 10/Mar/17 ]

For the records, the testing done in the team was on the production demo instance. Never did we enable `magnolia.develop`, as this would obviously have biaised the results. We could no longer see that issue on AdminCentral. The only case that might be remaining is if you have a combination of `magnolia.develop=true` and IE11 (and HTTPS), but that's not a case we think affects anybody.

Now as far as using WOFF on a public website, how could it be an issue? Cache will be enabled, no Pragma header will be set, IE will get the font just fine. Just like with 5.5.2 AdminCentral. Or am I missing something?

Comment by Maxime Michel [ 10/Mar/17 ]

Having tried it, I can now confirm that:

  • IE11 + HTTPS + `magnolia.develop=true` will see the AdminCentral font disappear
  • IE11 + HTTPS + `magnolia.develop=false` won't see the travel demo font disappear, even when tweaked to have the font served by Magnolia rather than Google's CDN
Generated at Mon Feb 12 09:13:32 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.