Home → General →

scheme relative URL's redux

• Edit

rrhill

24 Feb, 2011 02:13 AM

This topic was discussed at http://help.hannonhill.com/discussions/general/22-scheme-relative-uris but the discussion was closed and I think, without resolution. For more general information, see this prior discussion.

We have found that using scheme-relative URL's (of form //site/path instead of http://site/path) works perfectly well if the links are in a template local to the site. However, If the template is housed in a central "model" site and a site accesses that template cross site, Cascade strips the preceding "/" of the double slashes in the URL, so it becomes /sever/path rather than //server/path

This is the same as reported on the closed discussion. Bit with the additional information that Cascade is fine with scheme relative URL's as long as the template is local.

Turns out if we use three preceding slashes, Cascade strips one and all is good. Sorta. We don't trust it. Assuming its a bug and we use the three slash track, when the bug is fixed, all of our sites are trashed. We are in the middle of a major template site redesign and had hoped the scheme-relative links would fix our issues with mixed content elegantly. So, we need to know why this is occurring and how to proceed with confidence!

1. 1 Posted by rrhill on 25 Feb, 2011 07:22 PM

   

   More: Turns out we can include all of the off-site content using https calls, even on non-https pages. If a page is served using https and off-site content is included from a non-https site, browsers will report the mixed content issue. However, if the off-site content is served via https, then it doesn't matter if the page including that content is served via http or https. The browsers are fine with that. Makes sense.

   So, the solution is to always serve the external, global/common content from a https-enabled webserver and always include the content in Cascade using https calls.

   • Edit

2. rrhill closed this discussion on 10 Mar, 2011 04:43 PM.