This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

XHR post blocked when Captcha is selected

  • 2 iimpendulo
  • 0 inale ngxaki
  • 62 views
  • Impendulo yokugqibela ngu spliffys

more options

Hello, I am struggling with a bug specific to Firefox (108.0.2) in which I have an XHR Post that is being blocked by dev tools only when a google captcha is selected. Here is the website that the bug is happening on. Per comment suggestions I've added a screen shot of the URL being blocked in dev tools.

My overall goal is to have this form post it's action and post the form data to another endpoint (https://beeceptor.com/console/preferencecenter). I am able to successfully post data to beeceptor with the captcha selected when testing in Chrome, but as stated not Firefox. If the form is submitted without the captcha selected the data is successfully posting to the beeceptor endpoint- this behavior is happening with both Chrome and Firefox which I am sure means something is wrong with my Javascript which can be resolved later.

Looking at the console in Firefox I am consistently seeing a XHR Post blocked to the beeceptor url with captcha selected. I have gone through several iterations of this code to resolve the issue, none of which have successfully worked. After many, many, hours of digging I have done the following to no avail.

  • Cleared Cache
  • Ran in Safemode then back to regular mode (one article this appeared to fix for a user)
  • Ran in Private Browsing
  • Adjusted CORS accordingly

There are more items I've attempted that I can't remember off the top of my head.

Any help with this would be greatly appreciated as I have hit a wall.

Hello, I am struggling with a bug specific to Firefox (108.0.2) in which I have an XHR Post that is being blocked by dev tools only when a google captcha is selected. [https://www.pages09.net/grandamericahotelsandresorts/DEV-SBSFDCPrefCenter/Preference_Center/ Here is the website] that the bug is happening on. Per comment suggestions I've added a screen shot of the URL being blocked in dev tools. My overall goal is to have this form post it's action and post the form data to another endpoint (https://beeceptor.com/console/preferencecenter). I am able to successfully post data to beeceptor with the captcha selected when testing in Chrome, but as stated not Firefox. If the form is submitted without the captcha selected the data is successfully posting to the beeceptor endpoint- this behavior is happening with both Chrome and Firefox which I am sure means something is wrong with my Javascript which can be resolved later. Looking at the console in Firefox I am consistently seeing a XHR Post blocked to the beeceptor url with captcha selected. I have gone through several iterations of this code to resolve the issue, none of which have successfully worked. After many, many, hours of digging I have done the following to no avail. * Cleared Cache * Ran in Safemode then back to regular mode (one article this appeared to fix for a user) * Ran in Private Browsing * Adjusted CORS accordingly There are more items I've attempted that I can't remember off the top of my head. Any help with this would be greatly appreciated as I have hit a wall.
Iqhotyoshelwe imifanekiso ekwisikrini

Ilungisiwe ngu spliffys

Isisombulu esikhethiweyo

I found the root issue of this to be stemming form jquery's validate plugin. Cleaning up the javascript resolved this issue. Hopefully this helps someone else in the future.

Funda le mpendulo kwimeko leyo 👍 0

All Replies (2)

more options

Thanks Dropa, I've included a screen shot with the original question now.

more options

Isisombululo esiKhethiweyo

I found the root issue of this to be stemming form jquery's validate plugin. Cleaning up the javascript resolved this issue. Hopefully this helps someone else in the future.