Mixed content

[fboldrin]

Hello, Is there a way to solve the mixed content error with the plugin ? Our Omeka installation use only https. The neatline-time plugin doesn't work properly because the browser doesn't allow mixed content. We have a workaround by disabling the security (allow insecure scripts) within the browser. Thank you in advance Best regards Fabian

[jamiefolsom]

Hi @jeremyboggs,

@akstuhl points out that it would appear that this error is due to a hard-coded URI which includes the protocol, located here.

I've forked NeatlineTime to Performant, and we'll open a PR from there. Are there other instances of this issue that you know of?

Thanks!

Jamie

[jeremyboggs]

@jamiefolsom I dont' think so. We might look in the nl-widget-Simile, but I didn't see anything similar in a cursory glance.

We might also see if @Daniel-KM's fork of NeatlineTime solves this issue. Either way, we should move this issue off Neatline, and to NeatlineTime.

[jamiefolsom]

@jeremyboggs 👍 thanks!

[akstuhl]

We were seeing mixed content errors for Neatline assets when loading Neatline staging over https (asset URLs were still created using plain http), but this appears to be an Omeka issue rather than Neatline. Per this forum discussion, adding SetEnv HTTPS "on" to .htaccess resolved the errors when loading over https. This strategy means all asset requests use https, which created CORS errors (only for font assets, for some reason). I resolved that with the additional lines in .htaccess:

<FilesMatch ".(eot|ttf|otf|woff)">
    Header set Access-Control-Allow-Origin "*"
</FilesMatch>

After reading this Omeka issue thread, I suspect that this could be a specific clash with how Heroku handles SSL, and Omeka instances on other hosting services might not need such a workaround.

[jeremyboggs]

Let's update the documentation to include these suggestions.

[jamiefolsom]

@akstuhl do you need access to the documentation repo?

[akstuhl]

Thanks @jamiefolsom, I think I do need access.

[jamiefolsom]

@jeremyboggs could @akstuhl have access to https://github.com/scholarslab/neatline-documentation, to get this updated?

[jeremyboggs]

@jamiefolsom Just invited @akstuhl to the Performat team on the SLab github, which would give him (and you) admin on Neatline and the documentation repo.