Resolved My https not work every page

[Anup Roy]

Hi,
I have a commercial webpage few month ago i convert http to https for better secure, but my every page not work https. Where the problem is anyone can suggest me?

 

[UFHH01]

Hi Anup Roy,

but my every page not work https

The site is still served over "HTTPS", otherwise you would not see the URL "https://....."

But you sure want to know, why the "SECURE" ( green bar ) is missing at the described page?
Actually, this is very simple:

Mixed content
The site includes HTTP resources.
Reload the page to record requests for HTTP resources.

Mixed Content: The page at 'https://www.clippingpathoutsource.com/blog/blog.html' was loaded over HTTPS, but requested an insecure image 'http://feeds.wordpress.com/1.0/comments/clippingpathoutsource.wordpress.com/139/'. This content should also be served over HTTPS.
blog.html:223

Mixed Content: The page at 'https://www.clippingpathoutsource.com/blog/blog.html' was loaded over HTTPS, but requested an insecure image 'http://feeds.wordpress.com/1.0/comments/clippingpathoutsource.wordpress.com/126/'. This content should also be served over HTTPS.
blog.html:240

Mixed Content: The page at 'https://www.clippingpathoutsource.com/blog/blog.html' was loaded over HTTPS, but requested an insecure image 'http://feeds.wordpress.com/1.0/comments/clippingpathoutsource.wordpress.com/119/'. This content should also be served over HTTPS.
blog.html:263

Mixed Content: The page at 'https://www.clippingpathoutsource.com/blog/blog.html' was loaded over HTTPS, but requested an insecure image 'http://feeds.wordpress.com/1.0/comments/clippingpathoutsource.wordpress.com/110/'. This content should also be served over HTTPS.
blog.html:284

Mixed Content: The page at 'https://www.clippingpathoutsource.com/blog/blog.html' was loaded over HTTPS, but requested an insecure image 'http://feeds.wordpress.com/1.0/comments/clippingpathoutsource.wordpress.com/98/'. This content should also be served over HTTPS.
blog.html:310

Mixed Content: The page at 'https://www.clippingpathoutsource.com/blog/blog.html' was loaded over HTTPS, but requested an insecure image 'http://feeds.wordpress.com/1.0/comments/clippingpathoutsource.wordpress.com/84/'. This content should also be served over HTTPS.
blog.html:323

Mixed Content: The page at 'https://www.clippingpathoutsource.com/blog/blog.html' was loaded over HTTPS, but requested an insecure image 'http://feeds.wordpress.com/1.0/comments/clippingpathoutsource.wordpress.com/79/'. This content should also be served over HTTPS.
blog.html:339

Mixed Content: The page at 'https://www.clippingpathoutsource.com/blog/blog.html' was loaded over HTTPS, but requested an insecure image 'http://feeds.wordpress.com/1.0/comments/clippingpathoutsource.wordpress.com/76/'. This content should also be served over HTTPS.
blog.html:350

Mixed Content: The page at 'https://www.clippingpathoutsource.com/blog/blog.html' was loaded over HTTPS, but requested an insecure image 'http://feeds.wordpress.com/1.0/comments/clippingpathoutsource.wordpress.com/70/'. This content should also be served over HTTPS.

 

[Anup Roy]

Yes, I want to see Green bar, I am not clear about your solution, please describe easily in a few words.

 

[UFHH01]

Hi Anup Roy,

there is no solution given with my previous post. I just point you to the fact, that you implemented "HTTP" - sources as for example:

http://feeds.wordpress.com/1.0/comments/clippingpathoutsource.wordpress.com/...

Change the image / feed - URL to "HTTPS" - URLs and you should be fine.

 

[Anup Roy]

Hi Anup Roy,

there is no solution given with my previous post. I just point you to the fact, that you implemented "HTTP" - sources as for example:

http://feeds.wordpress.com/1.0/comments/clippingpathoutsource.wordpress.com/...

Change the image / feed - URL to "HTTPS" - URLs and you should be fine.

Thanks for your patient.

 

[netsol]

Some of your sites probably still include resources via http://. This is called mixed content, and most browsers won’t show the lock for pages with mixed content. You will have to make sure your site includes all resources via https:// or protocol-relative URLs (e.g. <script src="//example.com/script.js">).

 

[Skynatstech]

The error is because some of your contents in the website is using HTTP protocol instead of HTTPS. Update all URLs to https:// will resolve the issue.