Is there someone who has already passed on https? I would like to ask how Google reacted to the change (positions in the search engine)?

Regards

After the transition, I did not notice the difference. More for yourself and go to html5.
Here's the topic:
Https://webmasters.googleblog.com/2014/08/https-as-ranking-signal.html
Https://support.google.com/webmasters/answer/34444?hl=en

hhttps://www.google.pl/?gws_rd=ssl#q=site:kulturystyka.org.pl/modules/news/article.php

every module redirection works fine but in news module is blank page, xoops 2.5.7, module news: 1,68 RC1

category redirect works fine but single article is blank page ...

Yes i felt something will be wrong, otherwise it would be too beautiful;)

http://www.kulturystyka.org.pl/modules/news/article.php?storyid=392 - redirection 301 STOP WORKS and other articles

http://www.kulturystyka.org.pl/modules/news/ - WORKS

http://www.kulturystyka.org.pl/modules/news/index.php?storytopic=34 - all categories WORKS

maybe with this redirect code is something wrong?


Now i switch off this code, because i'm afraid of google position, i will wait for your help

Thanks to all! Very useful info.

If you are seeing some images and not others, your server is telling your browser to no longer display the unsecured images.

You can verify by right clicking on the image or placeholder that does not display and the select your browsers Inspect option in the dropdown. Do you see a url that begins with http:// (unsecured) in the inspect code?

Now try this for an image you can see. Do you see https:// (secured) instead of http:// ?

If yes to both of your above tests, any changes made to httpd.conf or .htaccess to enforce TLS result in the browsers no longer being allowed to display unsecured content. That is because it will only honor secured content.

There is another possibility for this symptom.

If you renamed all http:// in your database dump to https:// as recommended above, but the external server associated with one of the url that you changed does not support https://, the associated content may not be served to your browser. It may even produce an error.

Quote:


This following t '://' allows php to build the url as either http:// if the system does not support TLS, or as https:// if it does support TLS.

For systems such as all my sites which are 100% hardccore SSL, I edit :// to https:// and no http: url construction is possible. Be judicioius. You still cannot use a https link to access an external resource that does not support https so you need a good overview and sense of your requirements, and what constraints you are willing to live with (some missing imagery or broken ssl lock display in the url bar).