Updating Landing page content during SSL implementation from http to https

[Vinod_Mahadeva]

Hi,

We're implementing SSL certificate and got more then 14K+ landing pages in our instance. once the SSL enabled we need to update all the images/hyperlinks/CSS files etc used in our landing pages from http to https. When I referred to REST API we need landing page ID (which I have) and content ID to update any landing page content, but for URL's I don't have any ID associated or we can't do this manually with 14k Landing pages. So is there anyone done this update during SSL implementation please advise if there are any alternative ways of doing it.

[SanfordWhiteman · Accepted solution]

The only way to avoid changing the pages is to run all your LPs via a reverse proxy which can change the response body on-the-fly.

Of course if you know how to do this you could've avoided using Marketo's SSL hosting in the first place. But you'd have to stack the 2 together.

Also don't forget about full URLs stored in tokens: if you have any of those, they'd have to be changed manually or via API as well.

[Vinod_Mahadeva]

Hi Sanford,

Thanks for responding with your comments, if we do reverse proxy there is no need for SSL enablement is what you're saying right ?

I don't see any API call which allows Link update or the landing pages created using free form template. Because in one of the update call it asks for Landing page ID and content ID, for free form there will not be content ID that we can reference.

We have built only few using guided landing page template and most of them are built on free form. Is there any way that I can accomplish this

[SanfordWhiteman]

The reverse proxy itself does SSL termination, so yes, that's why you would no longer technically need SSL between the proxy and Marketo (the next hop).

Still, in some cases an end-to-end security guarantee might be required due to corporate policy or regulations.

Anyway the point is this is the only way to ensure all your links are rewritten.