1203445 - SVG symbols are not displayed on https://quai10.org/

Status: RESOLVED DUPLICATE of bug 1247733

(Core :: SVG, defect)

Description

[Pierre Rudloff]

Attachment: Screenshot (with bug)

The first time I browse to https://quai10.org/ after opening my browser, all SVG symbols included with <use> are not displayed.
Sometimes, it is fixed with a reload, sometimes not.

I can reproduce with Firefox desktop 38 and 42 and Firefox Android 40.
I can't reproduce with Chrome.

On some computers, it seems to never happen when you type https://quai10.org/ in the location bar, but only when you just type quai10.org.

Comment 1

[Pierre Rudloff]

Attachment: Screenshot (without bug)

Comment 2

[Robert Longson [:longsonr]]

When it works the content-length returned in the http header is 9119. When it doesn't work it's 9117. 

Either there's two different files returned perhaps because they are coming from different servers split by a load balancer or the server is returning the wrong data sometimes. In either case it's a server error.

Comment 3

[Pierre Rudloff]

The Content-Length header might be different because some content on the page is random.

Here is a more simple testcase: https://quai10.org/testcase.html
With this, the header is the same every time (5232).

Comment 4

[Robert Longson [:longsonr]]

The simple testcase displays correctly every time for me as far as I can tell.

Comment 5

[Pierre Rudloff]

I can reproduce with the testcase on several different computers (Debian, Ubuntu, OSX).
These steps seem to help reproduce it:
1. Browse to https://quai10.org/testcase.html
2. Browse to http://quai10.org/testcase.html (HSTS will then redirect to HTTPS)

Comment 6

[alexspark86]

The bug is reproduced with steps of Pierre Rudloff.

Comment 7

[qtuzov]

Maybe you can provide some workaround?

Comment 8

[Botond Ballo [:botond]]

:dholbert, is this a dupe of bug 1247733 as well?

Comment 9

[Daniel Holbert [:dholbert]]

Yes. Thanks!

(I confirmed that this is fixed in Nightly 48, too. It should be fixed all the way back to the current release --  Firefox 45 -- via bug 1249452 [haven't tested that here, but I expect that to be the case].)