[
https://issues.apache.org/jira/browse/GUACAMOLE-347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16089296#comment-16089296
]
Michael Jumper commented on GUACAMOLE-347:
------------------------------------------
The lack of {{window.location.origin}} in IE11 is a bug in IE, however IE10
does not support {{window.location.origin}} at all. So long as IE10 remains a
supported browser for Guacamole, this needs to be fixed.
> IE may lack window.location.origin
> ----------------------------------
>
> Key: GUACAMOLE-347
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-347
> Project: Guacamole
> Issue Type: Bug
> Reporter: Michael Jumper
>
> From GUACAMOLE-327:
> {quote}
> Internet Explorer, including 11, doesn't have support for location.origin so
> when trying to build the URL for the XMLHttpRequests in
> tunnelService.downloadStream and tunnelService.uploadToStream, the string
> "undefined" gets prepended onto the URL, rendering that functionality
> unusable.
> The workaround/polyfill for this is pretty simple and well documented on the
> web and is basically:
> {code:javascript}
> if (!window.location.origin) {
> window.location.origin = window.location.protocol + '//' +
> window.location.hostname + (window.location.port ? (':' +
> window.location.port) : '');
> }
> {code}
> {quote}
> In addition to the above, there are other locations within the Guacamole web
> application which use {{window.location.origin}} which will need to be
> corrected. In particular:
> * Reformatting of query parameters for AngularJS
> * Generation of share links
> * Generation of download/upload URLs for streams
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
