Avatar for Username

Rechercher dans l’assistance

Évitez les escroqueries à l’assistance. Nous ne vous demanderons jamais d’appeler ou d’envoyer un SMS à un numéro de téléphone ou de partager des informations personnelles. Veuillez signaler toute activité suspecte en utilisant l’option « Signaler un abus ».

En savoir plus

Ce sujet de discussion a été archivé. Veuillez poser une nouvelle question si vous avez besoin d’aide.

navigator.sendBeacon() failing on secure websites

  • 3 réponses
  • 1 a ce problème
  • 9 vues
  • Dernière réponse par jkns

jkns
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.

Toutes les réponses (3)

guigs
guigs
more options

Try stackoverflow.com if this is not helpful. https://developer.mozilla.org/en-US/docs/Web/API/Beacon_API

jkns
jkns Auteur de la question
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

jkns
jkns Auteur de la question
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