Protei/PromucFlow_constructor
2
0
Fork 0
Code Issues Pull Requests Actions 2 Packages Projects Releases Wiki Activity

chore: restrict when /usage-pulse can be fired (#19029)

Browse Source
This commit is contained in:
f0c1s 2022-12-19 14:39:27 +05:30 committed by GitHub
parent c5c8734dc1
commit 0f56f054e0
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 18 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

25
app/client/public/logger.js
View File

@ -15,22 +15,31 @@ function getCurrentUTCHourTimestamp() {
const PULSE_API_ENDPOINT = "/api/v1/usage-pulse";
// Use standard fetch to POST (fire and forget)
/**
* Sends HTTP pulse to the server, when beaconAPI is not available.
* Fire and forget.
*/
function sendHTTPPulse() {
fetch(PULSE_API_ENDPOINT, {
method: "POST",
credentials: "same-origin",
})
.then(() => {
// Fire and forget
})
.catch(() => {
// Ignore errors; fire and forget
});
}
// Use the Beacon API to POST (fire and forget)
/**
* Sends a usage-pulse to the server using the Beacon API.
* If the Beacon API is not available, falls back to a standard fetch.
* Note: Only sends pulse when user is on "/app/" pages: editor and viewer.
*/
function sendPulse() {
const url = PULSE_API_ENDPOINT;
// In case the beacon fails to queue, use HTTPRequest
// TODO(abhinav): What about when the request itself fails?
if (!navigator.sendBeacon(url)) {
sendHTTPPulse();
if (window.location.href.includes("/app/")) {
navigator.sendBeacon(PULSE_API_ENDPOINT, "") || sendHTTPPulse();
}
}