5

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 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 https://, 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 http:// (FF 38). As well, I have yet to see any mixed-content warnings as a result of having http://.

With that in mind

  • Should I change these instances of http:// to https://?
  • Will W3C support HTTPS for these resources?

migrated from serverfault.com Apr 11 '15 at 22:50

This question came from our site for system and network administrators.

8

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.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.