Remove HTTP: Fix Mixed Content Warning

설명

Remove HTTP is a plugin that automatically scans and removes both http: and https: protocols from all links. This helps resolve websites that are having “mixed content warnings” which is when the website has assets (images, JavaScript, and CSS) loading both HTTP and HTTPS.

No changes to the links are made in the database. Simply install and activate the plugin and the changes will be immediate. Links that have http:// or https:// will only have //, making them protocol relative URLs. Below is a before and after example.

Before

<link rel='stylesheet' href='https://example.com/style.css' type='text/css' />
<script type='text/javascript' src='http://example.com/script.js'></script>
<a href="https://example.com" title="Example">Example</a>
<img src="http://example.com/image.jpg" width="150" height="50" />

After

<link rel='stylesheet' href='//example.com/style.css' type='text/css' />
<script type='text/javascript' src='//example.com/script.js'></script>
<a href="//example.com" title="Example">Example</a>
<img src="//example.com/image.jpg" width="150" height="50" />

Switch to Relative URLs

There is an option (under the General settings) to change internal links to relative URLs.

Contribute on GitHub

Want to help improve this plugin? Head over to our GitHub page.

설치

  1. Upload the plugin to the /wp-content/plugins/ directory.
  2. Activate the plugin through the Plugins menu in WordPress.
  3. Let it settle in for a minute and be amazed.

FAQ

What is mixed content?

According to Google:

Mixed content occurs when initial HTML is loaded over a secure HTTPS connection, but other resources (such as images, videos, stylesheets, scripts) are loaded over an insecure HTTP connection. This is called mixed content because both HTTP and HTTPS content are being loaded to display the same page, and the initial request was secure over HTTPS. Modern browsers display warnings about this type of content to indicate to the user that this page contains insecure resources.

How can I make my website fully SSL (on https://)?

You can actually remove the dependency of this plugin by following these step-by-step instructions below:

https://wordpress.stackexchange.com/a/238842/98212

It’s slightly technical because you’ll need to connect to your website’s host file through an FTP (such as FileZilla). After that, all of your links will be pointing towards your new HTTPS protocol.

후기

2020년 July 23일
plugin has an option to ignore externall but no option to ignore for internal links.. plzz add option to ignore for internall links...
2018년 April 17일
This really worked for me! Thanks a lot! Now I wonder if I dare to disable the wordpress-https plugin, or not...
2018년 April 4일
Seemed to work perfectly as http and https were actually striped site wide not only on the front end but surprisingly in even on the back. Database links all seem ok once deactivated which is a good thing. Had to deactivate as it caused some links to source articles from no longer working which is a bad thing. Suggestions: - Whitelist as someone mentioned would be great. - Also an option to maybe do images only for anyone using external images sources - Option to not change links on backend (admin)
2017년 October 22일
Shame this plugin doesn't have a 5* rating due to a few 1* reviews which aren't helpful/fair. Worked as intended, and saved me a bunch of time. Thank-you!
모든 19 평가 읽기

기여자 & 개발자

“Remove HTTP: Fix Mixed Content Warning”(은)는 오픈 소스 소프트웨어입니다. 다음의 사람들이 이 플러그인에 기여하였습니다.

기여자

자국어로 “Remove HTTP: Fix Mixed Content Warning”(을)를 번역하십시오.

개발에 관심이 있으십니까?

코드 탐색하기는, SVN 저장소를 확인하시거나, 개발 기록RSS로 구독하십시오.

변경이력

2.2.0

2020-04-06

  • Protocol is only removed on frontend #11
  • Fix: Settings not showing under Site Address (URL)
  • Fix: Settings icon is enlarged on Plugin page #9

2.1.1

2017-09-09

  • Added support for relative domain paths

2.1.0

2017-04-09

  • Restored option to ignore external links

2.0.0

2017-03-28

  • Feature: Switch between protocol-relative or relative URLs
  • Ignore <link> tags with rel="canonical" because they must be absolute URLs
  • Fix: Links in “style” tags weren’t affected