[Bug]: Concurrent requests to the same URLs are not sent at the same time

[kadirgun]

Preflight Checklist

• I have read the Contributing Guidelines for this project.
• I agree to follow the Code of Conduct that this project adheres to.
• I have searched the issue tracker for a bug report that matches the one I want to file, without success.

Electron Version

30.0.2

What operating system are you using?

Windows

Operating System Version

Windows 11 23H2

What arch are you using?

x64

Last Known Working Electron version

No response

Expected Behavior

When I send requests to the same URL at the same time via Google Chrome 124.0.6367.119, all requests are processed at the same time.

Actual Behavior

Likewise, in the electron browser window, only 1 request is processed at a time.

As expected, requests sent to different URL addresses are sent at the same time.

I'm not sure if this is a bug or not. It could be a security setting in Chrome.

Testcase Gist URL

https://gist.github.com/kadirgun/14b259f9c8651401a321c79a2a957ac1

No response

Additional Information

No response

[electron-issue-triage]

Hello @kadirgun. Thanks for reporting this and helping to make Electron better!

Would it be possible for you to make a standalone testcase with only the code necessary to reproduce the issue? For example, Electron Fiddle is a great tool for making small test cases and makes it easy to publish your test case to a gist that Electron maintainers can use.

Stand-alone test cases make fixing issues go more smoothly: it ensure everyone's looking at the same issue, it removes all unnecessary variables from the equation, and it can also provide the basis for automated regression tests.

Now adding the blocked/need-repro Needs a test case to reproduce the bug label for this reason. After you make a test case, please link to it in a followup comment. This issue will be closed in 10 days if the above is not addressed.

[kadirgun]

https://gist.github.com/kadirgun/14b259f9c8651401a321c79a2a957ac1

[kadirgun]

The problem seems to be cache related. When I checked the disable cache option the problem was solved.