How best to organize the work not all sections of the site on Yii via HTTPS?

A comprehensive website (portal) for Yii 1.x.

It is necessary to provide work through the Protocol HTTPS on only some sections of the site: admin panel, easy customization, registration form on the website

And all anything, but the architecture is modular, for example the admin module - is responsible for the work of the admin interface, at the same time, there are modules pages, galleries, articles, etc. - at the same time in one module it turns out there are as implementation of Front-End interface and Back-End interface (interfaces for the admin). To pick each module and rewrite the links in the Back-End interfaces is the large amount of work!

Maybe advise something to reduce the amount of routine work to change links http to https in each of the Back-End interface?

While comes to mind only one idea, each Back-End interfaces have a login page (login to your Personal account, sign in aminco, the entrance to the registration page) is to rewrite these links to https, and then in functionality to take into account in terms of http_referer with HTTPS or HTTP was the entrance? And if HTTPS then on the fly to fix all the links by changing HTTP to HTTPS. But in this case after login in the admin area or private office remains the possibility of an alternative to apply to any file via HTTP that is not too much trouble, but still.
July 9th 19 at 12:50

Related questions

More answers about "How best to organize the work not all sections of the site on Yii via HTTPS?"
1 answer
July 9th 19 at 12:52
and why not all over https?
In principle not a problem but in this case, any pitfalls? For example, with optimization for PS (the site has a great age and a good position in I and G)? - murray.Okune commented on July 9th 19 at 12:55
: as far as I know, Google is very favourable to https sites. but then it is better to create a separate question with the tag type "search engine optimization"... - mona commented on July 9th 19 at 12:58
: Full support ! Because you need HTTPS to encrypt traffic that someone snatched him and not stolen data. Now think about it: people went to https on the login page, I Selaginella, got the authorization cookie. Then switched to non-https page - and here it cook, catch as much as you!

If you do, then once the whole site, it is technically easier. As for the search engines - don't know, but I think that the actual presence of https is only a plus to the site. - Freeman.Stark80 commented on July 9th 19 at 13:01

Find more questions by tags HTTPSComputer networksYii