Summary: | Errors loading script under https in chrome | ||
---|---|---|---|
Product: | Koha | Reporter: | Martin Renvoize (ashimema) <martin.renvoize> |
Component: | OPAC | Assignee: | Owen Leonard <oleonard> |
Status: | CLOSED FIXED | QA Contact: | Testopia <testopia> |
Severity: | enhancement | ||
Priority: | P5 - low | CC: | magnus, mtompset |
Version: | Main | ||
Hardware: | All | ||
OS: | All | ||
Change sponsored?: | --- | Patch complexity: | --- |
Documentation contact: | Documentation submission: | ||
Text to go in the release notes: | Version(s) released in: | ||
Circulation function: |
Description
Martin Renvoize (ashimema)
2014-05-13 09:37:53 UTC
Not that this is the best solution, but perhaps adding: AddType text/javascript .js in the appropriate apache configuration files would work? (http://stackoverflow.com/questions/3467404/chrome-says-resource-interpreted-as-script-but-transferred-with-mime-type-text) I haven't tried it. I could recreate the error messages in the Chromium console on my local dev install, which is not using https. No sign of any warnings in Firefox, though. Is this bug still valid? I don't see any errors when I look at our OPAC in Chrome. |