Hey 馃憢
I develop and maintain software that uses Readium and believe this issue is a result of upgrade-insecure-requests being unconditionally added to the security policy on the frame. I made a tentative fix on a fork that makes it conditional via a new config upgradeInsecureRequests that passes it down, but wanted to open an issue before assuming the change would be welcome in a PR. The default should preserve the current behavior (always upgrade).
This seems related-ish to #120, though the referenced code snippet there is what I see on the develop branch so maybe that one is already resolved.
Thank you for all the work across all the Readium toolkits!
Hey 馃憢
I develop and maintain software that uses Readium and believe this issue is a result of
upgrade-insecure-requestsbeing unconditionally added to the security policy on the frame. I made a tentative fix on a fork that makes it conditional via a new configupgradeInsecureRequeststhat passes it down, but wanted to open an issue before assuming the change would be welcome in a PR. The default should preserve the current behavior (alwaysupgrade).This seems related-ish to #120, though the referenced code snippet there is what I see on the develop branch so maybe that one is already resolved.
Thank you for all the work across all the Readium toolkits!