Avoid SSL security warning when using assets from other Matrix sites

(Tom Chadwin) #1

I have many sites on our Matrix installation, but all tend to use one single shared site for their SSL, to save on purchasing multiple certs. Applying designs and paint layouts from the origin sites to pages within the secure site obviously leads to browser SSL warnings.

 

What would be the best/easiest way to solve this:

  • link the assets also under the SSL site, in which case will Matrix serve them with the right site's URL?
  • apply web paths from the SSL site to the assets in the other sites, in which case ditto

Anything other ways of doing this, other than cloning everything and losing the ability to reskin across both origin and SSL sites in one go?

(Nic Hubbard) #2

You shouldn't have to clone anything. You can just link the assets under the SSL site. Although, if you are linking to those pages, Matrix will aways print the shortest link, so if the links to the non-ssl webpaths are shorter, it will use those.

(Tom Chadwin) #3

Now there's a nugget of info I didn't know - thanks, Nic. Having once brought down every site on our Matrix installation by applying a URL to the Designs folder which DNS wasn't not yet pointing to the box, this info would have been very useful at the time. I shall have to do some character counting and removing of directory structures. Never carried out competitive URL shortening before.

(Nic Hubbard) #4

I shall have to do some character counting and removing of directory structures. Never carried out competitive URL shortening before.

 

Well you can always just copy and paste the webpath in yourself instead of using a ./?a=, but that has its own issues.

(Tom Chadwin) #5

The issues being? That Matrix has to process all requests for files which could just have been served by Apache? Is that right? What other issues does ./?a= have?

(Nic Hubbard) #6

The issues being? That Matrix has to process all requests for files which could just have been served by Apache? Is that right? What other issues does ./?a= have?

 

Sorry, I meant that if the SSL URL was longer, then you will have an issue trying to use it in a link if you are using ./?a= or keywords, since Matrix will use a shorter webpath to that asset. I was just saying that you could statically type in that shorter URL into your page, rather than using a keyword. The issue with that is Matrix is no longer handling the linking, so if you changed or updated the webpath or moved the asset you would have a broken link.

 

Follow me?

(Tom Chadwin) #7

I do, yes. Threadnapping myself shamelessly, am I right about ./?a= having a performance hit?

(Nic Hubbard) #8

I do, yes. Threadnapping myself shamelessly, am I right about ./?a= having a performance hit?

 

I wouldn't think there is much performance issues with using that. You are worried about slow load times when using it?