Forms2.min.js intermittently giving 403 for some users | Community
Skip to main content
A
Anonymous
November 14, 2016
Solved

Forms2.min.js intermittently giving 403 for some users

  • November 14, 2016
  • 4 replies
  • 6886 views

Hi all,

We use the Marketo forms 2.0 on our website. On a few machines we have seen an error that reads:

When most people visit our site we do not see this error in the console, however, for at least 2 machines we've seen this. We've been able to fix it on each of the machines by having them physically type in https://app-sji.marketo.com/js/forms2/js/forms2.min.js into the browser. After that point the forms load for them. For all forms we are using the embed code provided by Marketo. Has anyone seen similar issues / know of a reasonable workaround? Is it necessary to edit the embed code provided by Marketo to have it work for all users all the time?

Stephen Ross,

Intradiem

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by SanfordWhiteman

Certainly this isn't a regular situation. Note that what you're manually typing is the URL, which isn't the first URL the browser requests when running from a non-SSL site.

On a non-SSL site, in a browser that has never visited your Marketo pod before, the browser will request the version and will receive a redirect from the Marketo server to the version.  On subsequent visits the browser will no longer request the version for Marketo but will request the version only. 

Because of the distinctly different expected behavior between the first and subsequent visits, this specific case can be very difficult to troubleshoot, because the http->https internal redirection persists in Incognito/Private windows as well.

I would recommend you hard-code (instead of the protocol-relative //) and see if you can repro the problem.

4 replies

M
mderosa
New Participant
November 25, 2019

Hi @Sanford Whiteman that would be great. I'll try to set up now. I can give you an uberconference link.

SanfordWhiteman
SanfordWhiteman
New Participant
November 25, 2019

JoinMe is better for me. I'm starting join.me/figureone now.

M
mderosa
New Participant
November 25, 2019

Ok, I'm on join.me/figureone. I don't see you, however. Let me know if there's a different link I should follow.

M
mderosa
New Participant
November 22, 2019

M
mderosa
New Participant
November 25, 2019

Hi @Sanford Whiteman‌, we intend to deploy some Marketo-related updates to our production site this evening, but are hesitant with one of our test users still getting this 403 error. Are there any other files we can provide for troubleshooting purposes?

SanfordWhiteman
SanfordWhiteman
New Participant
November 25, 2019

I don't know about files but if you want to get on a screenshare (on that person's machine) I can take a look.

M
mderosa
New Participant
November 21, 2019

Hi Sanford, we have a user who is running into this same 403 error. This is on a non-SSL site, where the reference to the forms2 js does not use https (and uses a Marketo domain alias for which SSL has been set up). Simply referencing the forms2 js script over https doesn't fix it for them (nor does having them put the https url in their browser). Of about 10 users we've tested, this is only happening to one and it is persistent for that user. Do you have any other insights as to why this may be happening or a possible work-around?

SanfordWhiteman
SanfordWhiteman
New Participant
November 22, 2019

Are they getting a CloudFlare page when they go straight to the URL (in a new tab)?

M
mderosa
New Participant
November 22, 2019

No they are not.

SanfordWhiteman
SanfordWhitemanAccepted solution
New Participant
November 14, 2016

Certainly this isn't a regular situation. Note that what you're manually typing is the URL, which isn't the first URL the browser requests when running from a non-SSL site.

On a non-SSL site, in a browser that has never visited your Marketo pod before, the browser will request the version and will receive a redirect from the Marketo server to the version.  On subsequent visits the browser will no longer request the version for Marketo but will request the version only. 

Because of the distinctly different expected behavior between the first and subsequent visits, this specific case can be very difficult to troubleshoot, because the http->https internal redirection persists in Incognito/Private windows as well.

I would recommend you hard-code (instead of the protocol-relative //) and see if you can repro the problem.

A
Anonymous
November 14, 2016

Hi Sanford.

I will make this as the correct answer for two reasons:

  1. Going to the location has fixed the problem for those for which it has occurred.
  2. I have reason to believe that our security platform, Sophos, which has been installed on each of the machines which have had this issue, may be interfering with the marketo files trying to load in the background.
SanfordWhiteman
SanfordWhiteman
New Participant
November 15, 2016

Thanks for the update. There could indeed be a malfunctioning antivirus signature/heuristic affecting this. Can't see what policy it would be trying to enforce, though.

Terms & ConditionsAccessibility statement

Loading footer...