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

Wannan tattunawa ta zama daɗaɗɗiya. Yi sabuwar tambaya idan ka na bukatar taimako.

navigator.sendBeacon() failing on secure websites

  • 3 amsoshi
  • 1 yana da wannan matsala
  • 1 view
  • Amsa ta ƙarshe daga jkns

more options

I'm trying to use the Beacon API (https://developer.mozilla.org/en-US/docs/Web/API/Beacon_API), but Firefox (13.1) on iPhone X (iOS 11.4.1) will not communicate with a secure site (https). E.g.

navigator.sendBeacon('http://xxxx.com', 'data'); will send a POST but navigator.sendBeacon('https://xxxx.com', 'data'); will NOT send a POST.

navigator.sendBeacon() returns true on both secure (https) and insecure (http) sites.

macOS Firefox and iPhone Safari work fine. I've contacted Apple and they say it's a Firefox issue.

I'm trying to use the Beacon API (https://developer.mozilla.org/en-US/docs/Web/API/Beacon_API), but Firefox (13.1) on iPhone X (iOS 11.4.1) will not communicate with a secure site (https). E.g. navigator.sendBeacon('http://xxxx.com', 'data'); will send a POST but navigator.sendBeacon('https://xxxx.com', 'data'); will NOT send a POST. navigator.sendBeacon() returns true on both secure (https) and insecure (http) sites. macOS Firefox and iPhone Safari work fine. I've contacted Apple and they say it's a Firefox issue.

All Replies (3)

more options
more options

Hi guigs,

I've already tried Stack Overflow but didn't get anything - https://stackoverflow.com/questions/51844586/navigator-sendbeacon-on-iphone-chrome-not-posting-to-secure-websites

jkns

more options

Chromium have investigated this and it is a WebKit issue. See comment for detailed explanation - https://bugs.chromium.org/p/chromium/issues/detail?id=878562#c17