Closed
Bug 1181316
Opened 10 years ago
Closed 10 years ago
svg <use> with local xlink:href does not render after 301 redirect from http to https
Categories
(Core :: SVG, defect)
Core
SVG
Tracking
()
RESOLVED
INVALID
People
(Reporter: kevinkevin, Unassigned)
Details
(Keywords: reproducible)
Attachments
(1 file)
|
2.46 KB,
text/html
|
Details |
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_4) AppleWebKit/600.7.12 (KHTML, like Gecko) Version/8.0.7 Safari/600.7.12
Steps to reproduce:
(HTML file attached)
On our server, when firefox references this page with an http url, it gets redirected to the https version of the page.
You can see this at http://roadster.com/rdtestsvg.html
This problem existed also in Firefox 38, and in 40 beta 1. It worked back in earlier versions of Firefox (36, I think).
Actual results:
The inline version of the svg displays correctly, but the svg elements with <use> that reference the svg content via xlink:href do not display.
Note that they do display if you go directly to https://roadster.com/rdtestsvg.html
Expected results:
All of the svg elements should display (look at the page with Safari or Chrome, for instance).
Comment 1•10 years ago
|
||
I can reproduce the problem on Nightly42.0a1 - Firefox4.
Steps to reproduce:
1. Start with newly created profile
2. Open http://roadster.com/rdtestsvg.html
--- correctly displayed
3. Open http://roadster.com/rdtestsvg.html again
--- reproduce this bug
Alternate Steps to reproduce:
1. Open New Private Window
2. Open http://roadster.com/rdtestsvg.html
--- correctly displayed
3. Open http://roadster.com/rdtestsvg.html again
--- reproduce this bug
Status: UNCONFIRMED → NEW
Component: Untriaged → SVG
Ever confirmed: true
Product: Firefox → Core
Version: 39 Branch → Trunk
Updated•10 years ago
|
Keywords: reproducible
Comment 2•10 years ago
|
||
<use> elements must be same origin (https://developer.mozilla.org/en-US/docs/Web/SVG/Element/use)
Different protocol = different origin (https://developer.mozilla.org/en-US/docs/Web/Security/Same-origin_policy)
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•