Hiya,
For various reasons we are deploying RDS 2012R2 via our shiny new SSL VPN portal provided by our Firewall, the firewall proxys and obscures the address of any URLs that are opened through it.
As a result when you try and browse to the rdweb url you get an error message in IE:
The XML page cannot be displayed. Cannot view XML input using XSL style sheet.....
If i do the same with Chrome it partially loads but spits out errors in the Developer Tools:
"Unsafe attempt to load URL https://InternalServerHostname.domain.com/RDWeb/Pages/en-US/RDWAStrings.xml from frame with URL https://sslVPNURL.domain.com/proxy/https/obscuredURL/RDWeb/Pages/en-US/login.aspx?ReturnURL=/RDWeb/Pages/en-US/Default.aspx Domains, protocols and ports must match"
So from doing research it does seem that issue is down to trying to load the XSL sheet from a URL that is different from the URL open in the browser - looking at it, it appears that the XSL performs a look up of the local host URL and uses that to then provide the html headers etc. that includes href="https://InternalServerHostname.domain.com/RDWeb/Pages/en-US/"
Has anyone encountered this before and if so how did you get round it (yes I am aware of the RD Gateway, we are trying to avoid using that if possible as our Firewall provides excellent logging that we can't get from the gateway). In my mind it involves modifying the XSL or aspx files so that either the XSL is embedded in the same file, or that the URLs are all set to relative not something based on a lookup. I know relative works as our intranet loads fine and all of the href's are relative.
Thoughts on postcards, and try to avoid mocking the use of an SSL VPN portal over the Gateway please.... :)
How many surrealists does it take to change a lightbulb?
Two - one to hold the bulb and the other to put the clocks in the bathtub.