Turning on Https - munchkin issues , landing page issues? | Community
Skip to main content
Darrell_Alfons2
Darrell_Alfons2
New Participant
June 20, 2017
Solved

Turning on Https - munchkin issues , landing page issues?

  • June 20, 2017
  • 1 reply
  • 3273 views

Looking through some of the previous posts and I'm a little confused.

If we turn on https for our site, will munchkin function ok?

Also, from other posts - it sounds like marketo landing pages will need a special certification. But what about wordpress pages with embedded marketo forms?

Any insight is appreciated thank you.

Best answer by SanfordWhiteman

Munchkin automatically loads securely if your page is secure (when you load an asset from a protocol-relative URL -- a URL that starts with '//' -- that means the asset will use the same protocol as the main document).

Similarly, your embedded forms should already be loading from protocol-relative // URLs. That's what the default embed code does. However, if you happen to have manually changed the embed code to load forms from, for example, your LP domain lp.example.com, then you need to either (a) make sure you have HTTPS running on your LP domain or (b) change back to //{appinstance}.marketo.com.

1 reply

SanfordWhiteman
SanfordWhitemanAccepted solution
New Participant
June 20, 2017

Munchkin automatically loads securely if your page is secure (when you load an asset from a protocol-relative URL -- a URL that starts with '//' -- that means the asset will use the same protocol as the main document).

Similarly, your embedded forms should already be loading from protocol-relative // URLs. That's what the default embed code does. However, if you happen to have manually changed the embed code to load forms from, for example, your LP domain lp.example.com, then you need to either (a) make sure you have HTTPS running on your LP domain or (b) change back to //{appinstance}.marketo.com.

Darrell_Alfons2
Darrell_Alfons2Author
New Participant
June 20, 2017

Thanks Sanford.

We have iframed marketo landing pages on wordpress pages so we could retain the form fill.

Looks like that is breaking now, so I assume it is because we need to get certified through Marketo first?

Then that should solve the problem?

SanfordWhiteman
SanfordWhiteman
New Participant
June 20, 2017

OK, that's not an embedded form, then -- IFRAMEs are entirely separate documents. From the standpoint of the main document you've embedded another HTML document (it doesn't care what's inside that doc, be it forms, images, JS, whatever).

In any case, if you can't include the IFRAME with relative // or explicit http​s://  (which would be true if you haven't purchased and uploaded an SSL cert to Marketo, paid, and waited for them to install it in your instance) then you're going to be out of luck for awhile.

"Certified" isn't really the term for this: it's "secured" by installing a cert.

Terms & ConditionsAccessibility statement

Loading footer...