How can I enforce case sensitivity for Puppeteer's HTTP header modifications?

I’m attempting to adjust the HTTP header in Puppeteer using a customized script snippet:

await clientPage.applyHeaders({
  'Accept-Language': 'en-US;q=0.95'
});

However, when I review Chrome’s network activity, the header appears as ‘accept-language’ entirely in lowercase, not preserving the case I specified. What approach can ensure the original header casing is maintained?

Through my own work with Puppeteer, I came to realize that this behavior is embedded in Chrome’s internal handling of headers. The browser automatically converts header names to lowercase, and there has been no straightforward method via Puppeteer to override this behavior. This limitation can be frustrating, particularly when precise header casing is needed for specific testing scenarios. My suggestion is to focus on device-level header handling or consider adjusting your validation processes to account for this automatic normalization.

im not sure if theres a workaround as chrome seems to force headers into lowercase by default; i tried fiddling with it but had no luck, might need to accept the browser behavior rather than forcing casE sensitivity.