Fix URL for docs.google.com #213
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
thanks for the fix! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In the filemanager.js file, at line 906, the Google viewer is accessed using HTTP:
ViewerObject.url = 'http://docs.google.com/viewer?url=' + encodeURIComponent (createPreviewUrl (resourceObject, false)) + '& embedded = true';Due to this when using the RichFilemanager in servers that force the use of HTTPS can occur problems in the visualization like the one below:
Mixed Content: The page at 'https://fm.svc.daspanel.site/' was loaded over HTTPS, but requested an insecure resource 'http://docs.google.com/viewer?url=https%3A%2F%2Ffm.svc.daspanel.site%2Fconn…_condominio_Abner_L._01_Q._51-FB.docx%26time%3D1501967130794&embedded=true'. This request has been blocked; the content must be served over HTTPS.