full or relative urls for images for SSL/https

I'm getting a yellow warning sign

[Lorel]

I'm not sure if this is the right category so please move it if there is a better one.

I set up my site for SSL/ HTTPS and it passed the whynopladlock text but now I notice that i'm getting a yellow warning when I view my pages because the images have relative urls and all other internal urls are absolute. I did it that way many years ago in case someone scraped my content so they wouldn't get the images.

Should I change all internal urls to relative?

[justpassing]

I did it that way many years ago in case someone scraped my content so they wouldn't get the images.

:) This was not preventing scrapers to get your images.

Should I change all internal urls to relative?

Yes, or edit all your page to change http:// to https:// , but it's good practice to have relative URLs. Image, CSS, JS, Fonts, any external file embed into your page.

nb: by "relative", the best practice is to have URLs relative to the root. Avoid URLs relative to the current page, or using "/../". This is fine, but harder to maintain.

For your TLS (SSL) validation, you can also use [ssllabs.com...] This will give you more information about your implementation of the protocol.

[not2easy]

It makes sense to me to use non-protocol links whenever possible. I removed all mention of http anything from my sites. Even external links work fine with // in place of http or https and it saves the trouble of converting the protocols when other sites update. There are still many non-https sites.

[Lorel]

thanks everyone.