Images uploaded in wordpress have http rather that https in URL - wordpress

When the chrome the developer tool on some of my web pages I get this warning
"The page at https://www.improvementskills.org/wordpress/whats-going-on-2/ displayed insecure content from http://abim3.improvementskills.org/wordpress/wp-content/uploads/2013/08/run_chart2.png.
www.improvementskills.org/wordpress/whats-going-on-2/:1"
I'm guessing this is because the image urls have http rather https. Whenever I upload new images in wordpress it gives it http as well. How do I go about fixing this? Thanks!

Update: The technique in my comment below is now an anti-pattern! Always use https. http://www.paulirish.com/2010/the-protocol-relative-url/
If you can edit your website's img tags, then remove "http:" from the src.
Bad
http://abim3.improvementskills.org/wordpress/wp-content/uploads/2013/08/run_chart2.png
Good
//abim3.improvementskills.org/wordpress/wp-content/uploads/2013/08/run_chart2.png
This way, the browser will call the image with https when needed, and http otherwise.

Related

Https: Weak Connection

I have a website on which users can write blog posts. For adding Images users can add the URL of an Image & image will be shown on their blog post.
But problem is that if a user inserts link of an image starting with http:// such as http://example.com/flower.jpg, browser shows a warning saying,
Your Connection to this site is not Fully Secure.
Attackers might be able to see the images you are looking at
& trick you by modifying them
I was wondering how can we force the browser to use the https:// version of site only from which image is being inserted to prevent this issue?
Or is there any other solution of this problem?
The best solution is probably to download the image and serve it from your own domain.
This also avoids issues due to hotlinking.
Alternatively you can try to replace http with https but there is no guarantee that the target website has a valid certificate or even a webserver listening there.

Insecure stylesheet WordPress

Im having problems with WordPress, I'm getting this error everywhere in the site, wp-admin, home dir and etc. I can't find a way to fix it because I cant see the valid URL of it. Error looks like this, I received it while trying to edit widget in widgets area wp-admin:
Mixed Content: The page at 'https://somesite.com/wp-admin/widgets.php' was loaded over HTTPS, but requested an insecure stylesheet 'http://somesite.com/?ver=1.11.4'. This request has been blocked; the content must be served over HTTPS.
Maybe anyone had similar problem, please help!
That error is generates by Google Chrome any time a website with SSL certificate (a website that uses HTTPS) try to call a URL without HTTPS, in your case you are calling somewhere in the code the URL "http://somesite.com/?ver=1.11.4" (probably in the menu or in the header).
There is a Wordpress plugin called "SSL Insecure Content Fixer" that can help you out in this problem, basically that plugin replace all the string "http://somesite.com/..." with "https://somesite.com/...".
So check it out, I think it will help you.
Problem was with redirects. If anyone has similar problems. Try to look at your server and htaccess redirects. Otherwise this was not your problem.

WordPress with ssl form let's encrypt, but homepage not fully secure. "Attackers might be able to see images.." message

Could you help me find out what to do with not fully secure message.
I have installed ssl certificate from let's encrypt, but my wordpress homepage has a message "Attackers might be able to see the images you're looking at on this site and trick you by modifying them".
The home page is still in development, with demo content. About what images chrome notification is telling? Something to do with cookies?
Thank you for your answers!
Edit: Does it have to do with the theme itself? Whole wordpress dashboard and login is served over proper secure ssl.
Sending images via http protocol is what triggers this issue. Using any content from a cdn that does not use https will also trigger this issue. This quote explains it pretty simply (the yellow padlock / warning of unencrypted content/images):
If a yellow padlock appears with a mini yield sign, the likely cause
is links in your site still refer to an unsecured page. Make sure that
all your images, menu items and links use https in the URL.
source
I would use a tool to help identify all non-encrypted file transports. One such tool would be something like Why No Padlock.
Did you enable https after installing WordPress? If so, you must change the WordPress address and Site Address under "General Settings" in WordPress. Make sure both addresses use https.
If your WordPress site address is set to use http, your server will force https but WordPress will serve certain images, like the favicon, over http. This triggers a "mixed content" warning.
I too had run into this issue. It appears there are many http: that need to be replaced with https:
You typically do this using a plugin called Better Search and Replace. Make sure you are adding colon (:) at the end of both http and https.
I found a working answer here
To check for issues on the chrome/opera inspection console (ctrl+shift+C) is also a great idea: I had setup all correctly and the issue was the footer image, not something you would check very often looking for this fix. I had applied SSL to many websites, sometimes the issue is just one simple link and this method helps find it.
I had the same problem where the home or index page was saying the page was not fully secure "Attackers might be able to see images blah blah blah"
After enabling https in general settings under site address and wordpress address I was still getting the insecure image warning on the index or home page.
The next step was to find out what images were not using the https ref on the index or home page.
In my case I viewed the page source of the page, by right mouse clicking the page in the chrome browser & looking for images url ref which were still showing http. I was using a sliding header and those images were showing http. So all I did was go into slider header in the appearance menu of the wordpress, and re-assign each of the header slider image for each frame. RE-checked the home page now the image urls were showing https. Bingo the secure lock symbol returned.
Obviously these image urls don't get updated via the general settings... which seems an oversight by whoever wrote the part of the word-press script.

HTTP link from HTTPS website

If I move a website to https so that it loads all resources (css, js, images, ...) via https, the browser will not pop any warning (I hope).
However, what if the content of my site is partially created by another users who may have already added links, e.g. <a href=http://anothersite.com>", that target websites without https. In such case, will the browser warn about mixed content?
And what about images, e.g. <img src=http://anothersite.com/img.jpg>"?
Thanks!
A link will not trigger mixed-content:
The content of that link is not displayed on your page, it doesn't modify the appearance or the functionalities of your page, so no reason to display a mixed-content warning.
(But if a secure version of that website is available, it's better to link directly to it, to avoid an insecure redirect)
But http images included in your https pages will trigger mixed-content warnings
What you cant do to prevent it partially, it using HSTS and https://www.w3.org/TR/upgrade-insecure-requests/

How to use http:// in https:// using iframe?

my website is ssl-enabled secure containg https://
Now i want to add a website link in my webpage using iframe which is in http://
How can i use it, Here problem is with http:// not working in https:// using iframe.
PLease give a solution
Thanks.
You can't, in many modern browsers because it is a major security issue. There's a workaround though, you can proxy the content via HTTPS. You have to create a something on HTTPS that fetches the unsecured content for you and passes it over TLS to the end user in the iframe. This, however, is not as trivial as it looks. Just fetching the content might not be enough, because the user might want/need to POST something back. And it's not just the content, but the headers too if you need to support cookies. And when the content you served over your proxy solution loads stuff via HTTP you end up with a mixed content warning.

Resources