11
justinebaby
Re: http to https

The modules useds: RMcommon and Mywords.

Thanks.

12
aerograf
Re: http to https
  • 2017/2/21 10:53

  • aerograf

  • Quite a regular

  • Posts: 214

  • Since: 2017/1/7 1


Quote:

geekwright wrote:
Quote:

aerograf wrote:
The ssl problem with mixed content, and decide now with the editors that have inserted links users excluding http: //. But not everyone supports ssl therefore looking for a solution through the above or /redirect.php?site=.
But not everything is working correctly.
Do ideas and solutions?


For internal links, where http links to your own site's content are embedded in your content, you can dump the database, replace all the occurrences, (i.e. change all http://example.com to https://example.com) and then reload it. There are also tools to do that in-place in the database. It is a one shot task, and really should only take a few minutes.

For external links where you are essentially hot linking someone else's content, you either accept the warnings, or you implement some sort of proxy. That is expensive (you end up carrying bandwidth to fetch and send out resources from the other sites, up from 0% to 200% of the cost) and it is risky, you have to engineer in protection to keep your site from being used as a proxy by other sites (a situation that could consume an entire month's bandwidth for a low price hosting plan in a matter of minutes.)

If you had a robust cache strategy, you could cut down the resource requirements. We do something like that for oEmbed content in XOOPS 2.6 already. That concept could be adapted to handle http proxying for this situation. But, 2.6 has a much more scalable cache already. It also has a more modular text sanitizer which could help in implementing the details.

It isn't impossible, but it is not something everyone would want to put into place. At this point, it isn't feasible to dedicate that much additional effort to the 2.5 series.

If the basic support for self hosted content over SSL doesn't work, that is a bug and will be fixed. A comprehensive proxy solution for remote hosted content is an enhancement which will be deferred to the next generation of XOOPS.

Thank you.
The issue with mixed content and resolved all the issues have been removed. Translated everything on ssl without problems. There were difficulties with JS, but they can be solved.

13
aerograf
Re: http to https
  • 2017/2/21 10:56

  • aerograf

  • Quite a regular

  • Posts: 214

  • Since: 2017/1/7 1


Quote:

justinebaby wrote:
Hello,

I try with your instruction, but some of images do not display correctly. Do you have somme idea else?

Regards.

If the problem is with the external picture, try src = "// ysite.org/img .....

14
justinebaby
Re: http to https

thanks,

But my probleme, i think it become:

style="background-image: url(<$post.image>);"

and the image from this can't be readed.

As in my previous post, the modules useds: RMcommon and Mywords.

Regards.

15
aerograf
Re: http to https
  • 2017/2/21 12:49

  • aerograf

  • Quite a regular

  • Posts: 214

  • Since: 2017/1/7 1


Quote:

justinebaby wrote:
thanks,

But my probleme, i think it become:

style="background-image: url(<$post.image>);"

and the image from this can't be readed.

As in my previous post, the modules useds: RMcommon and Mywords.

Regards.


Maybe so? <{$post.image}>

16
justinebaby
Re: http to https

yes, i do it, but still the same.

In http it work so find, but in https, no. The <{$post.image}> can't be displayed in image.

regards

17
aerograf
Re: http to https
  • 2017/2/21 13:02

  • aerograf

  • Quite a regular

  • Posts: 214

  • Since: 2017/1/7 1


If you are trying vstevit external image with the kernel, it will try to take it from https to take, but if the site does not support https and the images can not be. Try to to see the picture a direct link.

18
aerograf
Re: http to https
  • 2017/2/22 11:03

  • aerograf

  • Quite a regular

  • Posts: 214

  • Since: 2017/1/7 1


When you go to https in some modules do not work facebook comments, etc.
Corrected kaonkretno in News module in news_article.tpl template file, you must simply remove all http:, everything else remains the same. In other modules as well.

19
mjoel
Re: http to https
  • 2017/2/23 14:31

  • mjoel

  • Quite a regular

  • Posts: 325

  • Since: 2006/12/9


if we dont have https://

arent we suppose can't access it..and receive the message can't find server ?

i notice all XOOPS site can be access using https://

but with no styling

example:
https://www.xoops.org/

20
aerograf
Re: http to https
  • 2017/2/23 17:00

  • aerograf

  • Quite a regular

  • Posts: 214

  • Since: 2017/1/7 1


If all mainfile.php register in .htaccess and then it will work correctly

Login

Who's Online

137 user(s) are online (96 user(s) are browsing Support Forums)


Members: 0


Guests: 137


more...

Donat-O-Meter

Stats
Goal: $100.00
Due Date: Dec 31
Gross Amount: $0.00
Net Balance: $0.00
Left to go: $100.00
Make donations with PayPal!

Latest GitHub Commits