Note that on our side we are relying on the nsIIdentChannel.channelId to create the request id. If the channel id is not guaranteed to be unique, we might need to generate new unique ids.
Bug 1992348 Comment 1 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
The request id is set at https://searchfox.org/firefox-main/rev/2c8e9bccfd6ce951ceda8d46ab619f461b7fd0bc/remote/shared/NetworkRequest.sys.mjs#79-84 ```js this.#wrappedChannel = ChannelWrapper.get(channel); this.#redirectCount = this.#timedChannel.redirectCount; // The wrappedChannel id remains identical across redirects, whereas // nsIChannel.channelId is different for each and every request. this.#requestId = this.#wrappedChannel.id.toString(); ``` So it seems that the wrappedChannel might be reusing ids for data channels which have already been attributed to other channels?