: Schema links and HTTPS In the process of moving to 100% HTTPS on a site, I performed a site-wide search for http:// in an effort to find potential problems. One common class of instances included
In the process of moving to 100% HTTPS on a site, I performed a site-wide search for in an effort to find potential problems. One common class of instances included schema links (certainly there is a more proper way to say this), i.e.
<svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink">
My first instinct is to change these to , just as one might with intra-site links. However, if you request either of the URLs mentioned above using HTTPS, you are automatically redirected (307 Temporary Redirect) to the same URL with (FF 38). As well, I have yet to see any mixed-content warnings as a result of having .
With that in mind
Should I change these instances of to ?
Will W3C support HTTPS for these resources?
More posts by @Pierce454
1 Comments
Sorted by latest first Latest Oldest Best
These are no resources which get usually accessed by the browser but simply a fancy way to declare a name space, i.e. all SVG images share the same XML name space which is defined by the URL and same with xlink. This means you should treat any of these xmlns just as some kind of special string and leave them unchanged.
Terms of Use Create Support ticket Your support tickets Stock Market News! © vmapp.org2024 All Rights reserved.