Om de ûnderfining foar jo te ferbetterjen is tydlik de funksjonaliteit dan dizze website troch ûnderhâldswurk beheind. Wannear in artikel jo probleem net oplost en jo in fraach stelle wolle, kin ús stipemienskip jo helpe yn @FirefoxSupport op Twitter en /r/firefox op Reddit.

Sykje yn Support

Mij stipescams. Wy sille jo nea freegje in telefoannûmer te beljen, der in sms nei ta te stjoeren of persoanlike gegevens te dielen. Meld fertochte aktiviteit mei de opsje ‘Misbrûk melde’.

Mear ynfo

Dizze konversaasje is argivearre. Stel in nije fraach as jo help nedich hawwe.

navigator.sendBeacon() failing on secure websites

  • 3 antwurd
  • 1 hat dit probleem
  • 1 werjefte
  • Lêste antwurd fan 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.

Alle antwurden (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