Header Ordering Issue and Header Warning Mechanism

[alpgul]

The header I added or changed appears at the top, and the ordering is not being performed.
Additionally, when the header information containing the browser version changes, it should give a warning because the TLS information is fixed (chrome:125, firefox:128). Do you have any plans to update rustls for higher versions?

[barjin]

Hello and thank you for your interest in this project.

The header I added or changed appears at the top, and the ordering is not being performed

The header order for user-specified headers is not enforced. The implementation is the same for e.g. undici, Node.JS's native fetch implementation.

it should give a warning because the TLS information is fixed

I would rather not print warnings that are only related to the impersonation part of the library (and do not directly concern the requests being made). We are planning to add more (recent) browser fingerprints - see #99.

I'll close this issue in favour of #99 , feel free to add any ideas there.
Cheers!