The problem in the Chrome browser seems to be coming from a security feature, View\Server\sslgateway\conf\ and if it doesn’t yet exist, you can simply create it. Your View Connection and Security Servers in the folder C:\Program Files\VMware\VMware Settings are set in the file called locked.properties. To allow connections to succeed, register the extension by adding aĬhromeExtension entry to the locked.properties file”. Problem must have something to do with CORS and in specific with the Chromeīit further in the security documentation we’ll see an explanation for ourĬhrome problem: “Chrome extension clients set their initial Origin to their own We noticed that the direct URLĭidn’t gave problems, but de loadbalanced URL did. The first is a loadbalanced URL ( ) and the second is a direct URL to theĬonnection Server ( ). Secure (like there could be a man in the middle attack). Used, the policies can block access because the actions are considered not Used that is not the same as the listening domain, or when multiple domains are (CORS) as the feature that handles the policies in regard to HTTP request. The View Security document talks about Cross-Origin Resource Sharing In the VMware knowledge base, I found that the error has something to do with Worked, but Chrome threw the error: “Failed to connect to the Connection Everything was working except for theīLAST client on the Chrome browser. Our Horizon View environment from version 7.4 to version 7.5.1.
0 kommentar(er)
