$conf, $runtime; function_exists('chdir') AND chdir(APP_PATH); $r = 'mysql' == $conf['cache']['type'] ? website_set('runtime', $runtime) : cache_set('runtime', $runtime); } function runtime_truncate() { global $conf; 'mysql' == $conf['cache']['type'] ? website_set('runtime', '') : cache_delete('runtime'); } register_shutdown_function('runtime_save'); ?>ssl - All content is HTTPS, but browsers warn of HTTP mixed content|Programmer puzzle solving

Programmer puzzle solving

    最新消息：Welcome to the puzzle paradise for programmers! Here, a well-designed puzzle awaits you. From code logic puzzles to algorithmic challenges, each level is closely centered on the programmer's expertise and skills. Whether you're a novice programmer or an experienced tech guru, you'll find your own challenges on this site. In the process of solving puzzles, you can not only exercise your thinking skills, but also deepen your understanding and application of programming knowledge. Come to start this puzzle journey full of wisdom and challenges, with many programmers to compete with each other and show your programming wisdom! Translated with DeepL.com (free version)
    你的位置： HOME>matter>ssl - All content is HTTPS, but browsers warn of HTTP mixed content

    ssl - All content is HTTPS, but browsers warn of HTTP mixed content

    matteradmin7PV0评论
    Closed. This question is off-topic. It is not currently accepting answers.

    Questions that are too localized (such as syntax errors, code with restricted access, hacked sites, hosting or support issues) are not in scope. See how do I ask a good question?

    Closed 6 years ago.

    Improve this question

    Previously Chrome, Firefox, Edge, and other browsers showed our site as fully SSL/HTTPS secure. For some reason, they now warn about mixed content.

    But the content in question seems to be secure.

    This only affects a subset of the images on each page. Here's one example—a footer image. The image is entered like this on the WP back-end:

    <img src=";l=v4" />

    Firebug > Inspect Element shows:

    <img src=";l=v4">

    Firefox > View Source shows:

    <img src=";l=v4" />

    But Firebug > Network tab > Protocol column reports the image as:

    HTTP/1.1

    Chrome developer tools show the same results. What could cause this problem?

    Closed. This question is off-topic. It is not currently accepting answers.

    Questions that are too localized (such as syntax errors, code with restricted access, hacked sites, hosting or support issues) are not in scope. See how do I ask a good question?

    Closed 6 years ago.

    Improve this question

    Previously Chrome, Firefox, Edge, and other browsers showed our site as fully SSL/HTTPS secure. For some reason, they now warn about mixed content.

    But the content in question seems to be secure.

    This only affects a subset of the images on each page. Here's one example—a footer image. The image is entered like this on the WP back-end:

    <img src="https://widgets.guidestar/gximage2?o=7583405&l=v4" />

    Firebug > Inspect Element shows:

    <img src="https://widgets.guidestar/gximage2?o=7583405&l=v4">

    Firefox > View Source shows:

    <img src="https://widgets.guidestar/gximage2?o=7583405&l=v4" />

    But Firebug > Network tab > Protocol column reports the image as:

    HTTP/1.1

    Chrome developer tools show the same results. What could cause this problem?

    • ssl
    • https
    • http
    Share Improve this question asked Dec 27, 2018 at 23:11 Andy GieslerAndy Giesler 3091 gold badge2 silver badges11 bronze badges 1
    • you could try going doing a db search and replace all http://widget.guidestar with https://widget.guidestar – rudtek Commented Dec 28, 2018 at 22:31
    Add a comment  | 

    2 Answers 2

    Reset to default 3

    You have "www.wisconsinwetlands" URLs redirecting to insecure "http://wisconsinwetlands".

    The cases you have used these is in the images on the page. Every image that is set as "https://www." redirects to the insecure version.

    So while you do need to fix that and correctly configure your setup so that both "www" and non-www URLs are secure, you could quickly solve the problem by removing the www from your image URLs.

    301 redirects are the reason.

    In your site you have this image:

    https://www.wisconsinwetlands/wp-content/uploads/2015/04/mainheader7-1.jpg

    So it looks like HTTPS, but... If you go and visit that link, you'll get redirected with 301 to:

    http://wisconsinwetlands/wp-content/uploads/2015/04/mainheader7-1.jpg

    So it's not over HTTPS.

    Articles related to this article

    Post a comment

    comment list (0)

    1. No comments so far