Bug 19115 - Advanced editor - Rancor does not load on https
Summary: Advanced editor - Rancor does not load on https
Status: CLOSED INVALID
Alias: None
Product: Koha
Classification: Unclassified
Component: Cataloging (show other bugs)
Version: Main
Hardware: All All
: P5 - low normal (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-08-15 16:14 UTC by Josef Moravec
Modified: 2018-12-03 20:03 UTC (History)
4 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Josef Moravec 2017-08-15 16:14:24 UTC
There is mixed content error when you try to use Rancor on https. The editor does not load at all.
Comment 1 Katrin Fischer 2017-08-15 20:03:36 UTC
In 16.11.10 the advance cataloguing editor loads fine. Could it be some change made since? Is there an error visible in the developer tools client-side?
Comment 2 Josef Moravec 2017-08-16 05:21:27 UTC
(In reply to Katrin Fischer from comment #1)
> In 16.11.10 the advance cataloguing editor loads fine. Could it be some
> change made since? Is there an error visible in the developer tools
> client-side?

I have tried in 16.11.08 and 17.05.02 and problem is the same, chrome says this in the console:

Mixed Content: The page at 'https://koha-devel-test.knihovna-uo.cz/cgi-bin/koha/cataloguing/editor.pl' was loaded over HTTPS, but requested an insecure script 'http://koha-devel-test.knihovna-uo.cz/cgi-bin/koha/svc/cataloguing/framework?callback=define'. This request has been blocked; the content must be served over HTTPS.

Uncaught Error: Script error for: /cgi-bin/koha/svc/cataloguing/framework?frameworkcode=&callback=define
http://requirejs.org/docs/errors.html#scripterror
    at A (require.js:8)
    at HTMLScriptElement.onScriptError (require.js:29)
Comment 3 Katrin Fischer 2017-08-16 08:20:56 UTC
Hi Josef, I have tried again in Chrome, but can't see the error, everything seems to work ok here.
 
Are your baseUrls set to https://? We have sometimes seen weird behaviour when that was not the case.
Comment 4 Josef Moravec 2017-08-16 08:32:14 UTC
I checked all url-related sysprefs, (note the issue with staffClientBaseURL, see bug 16401)

but still has no luck...
Comment 5 Josef Moravec 2017-08-16 08:55:04 UTC
Is my configuration issues, sorry and thank Katrin and Robin (on IRC) for attention and advice.
Comment 6 Marjorie Barry-Vila 2018-02-01 19:08:00 UTC
(In reply to Josef Moravec from comment #5)
> Is my configuration issues, sorry and thank Katrin and Robin (on IRC) for
> attention and advice.

Hi Josef,

I have same problem in 17.05 but I understand that it depends on system configurations.
Can you tell me what are the good configurations?

Regards,
Marjorie
Comment 7 Liz Rea 2018-04-29 22:22:52 UTC
http://irc.koha-community.org/koha/2017-08-16#i_1962325

Here is the log of the discussion on IRC.
Comment 8 Liz Rea 2018-05-04 00:49:13 UTC
Just as an update here, this seems to happen when one is using a reverse proxy (as noted in the IRC conversation)

What I ended up having to do was putting in my HAProxy backend config, soemthing like

http-response replace-value Location ^http://(.*)$ https://\1

and reload haproxy. I'm feeling like this might not be the canonical way to fix this, but the other things suggested for similar problems didn't fix it, and this did.

So, take with a grain of salt, and I hope this bit of information helps people sort this problem in the future.