Dotclear

Ticket #2054 (closed defect: fixed)

Opened 11 years ago

Last modified 10 years ago

mixed content with post preview

Reported by: theYinYeti Owned by: team
Priority: normal Milestone: 2.9
Component: module:core Version: 2.7
Severity: normal Keywords: preview mixed content iframe
Cc:

Description

My dotclear is served on HTTP by Nginx / php-fpm. However, it is behind an SSL proxy, and when php-fpm is called, these settings are correctly set:

fastcgi_param HTTPS "on";
fastcgi_param SERVER_PORT "443";

Besides, DC_ADMIN_URL is now set to an HTTPS URL in inc/config.php.

Yet, when I want to preview a post, the black-bordered iframe is empty because its URL begins with HTTP instead of HTTPS.

I rate the severity as normal because the feature can still be used by opening the Preview link in a new tab/window (right-click menu).

Change History

comment:1 follow-up: ↓ 5 Changed 11 years ago by franck

Is your blog URL beginning with HTTPS ? See Blog's parameters.

comment:2 Changed 11 years ago by franck

  • Milestone changed from A definir to 2.7.4

comment:3 follow-up: ↓ 6 Changed 11 years ago by franck

May be fixed by the revisions [2019] and [2020]?

comment:4 Changed 11 years ago by bruno

  • Milestone changed from 2.7.4 to A definir

This issue is quite hard to solve : to avoid mixed content, a public adapter needs to be coded on admin side, and it implies lots of code.

Most of the time, you can force mixed content by clicking on a "shield" icon in your address bar.

I keep the issue opened, but it definitely won't be solved in 2.7.x, since it requires a big patch.

comment:5 in reply to: ↑ 1 Changed 11 years ago by theYinYeti

Replying to franck:

Is your blog URL beginning with HTTPS ? See Blog's parameters.

Hi! Sorry for the delay in answering. My blog’s URL begins with HTTP, not HTTPS, because I only use HTTPS when using the admin pages (although HTTPS can technically be used also on the other pages).

comment:6 in reply to: ↑ 3 Changed 11 years ago by theYinYeti

Replying to franck:

May be fixed by the revisions [2019] and [2020]?

From what I see when following the links, it seems highly unlikely that either of these changeset would solve the issue. For the time being, I’ll tell Firefox to just allow mixed content on my site, as suggested by bruno (thanks!)

comment:7 Changed 10 years ago by franck

In next 2.9, post preview will be opened in another tab/window if the admin is served over HTTPS and not the blog, in order to avoid mixed content and blank iframe.

comment:8 Changed 10 years ago by franck

  • Status changed from new to closed
  • Resolution set to fixed
  • Milestone changed from A definir to 2.9
Note: See TracTickets for help on using tickets.

Sites map