Re: [whatwg/fetch] Specify restriction for requests with keepalive set (#679)

Hello @yutakahirano,

We’re excited to share that Firefox is rolling out a new feature soon, and we’re aiming to include similar resource restrictions.

```

    - If the renderer process is processing more than 9 requests with keepalive set, we reject a new request with keepalive set initiated by fetch().
    - If the renderer process is processing more than 19 requests with keepalive set, we reject a new request with keepalive set.
        Note: The difference between fetch() + keepalive vs. SendBeacon is from a historical reason and we are going to have a unified restriction.
    - If Chrome is processing more than 255 requests with keepalive set, we reject a new request with keepalive set.

```
Could you let me know if these restrictions have changed? 
While we’re taking a slightly different route by limiting them based on origin and restricting requests per browser instance, we want to keep our limits comparable to Chrome’s.

By the way, what’s the plan for addressing the spec issue?

Thanks a million!

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/679#issuecomment-2262669042
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/fetch/issues/679/2262669042@github.com>