[Feature Request]: Allow changing default settings

[ytinyui]

Describe the feature / enhancement and how it would improve things

Currently, changing the values in tls_requests.settings has no effect because the default argument values are set only once at the time the function is defined.
Enabling this feature allows users to modify the default configuration without explicitly specifying the reverent arguments in every function call.
If you agree on this suggestion, I can implement this and create a PR later.

Describe how your proposal will work, with code and/or pseudo-code

The default settings should be evaluated at the time when the function is called. For example, in tls_requests.api.request:

def request(
    ...,
    timeout: TimeoutTypes = None,
) -> Response:
    if timeout is None:
        timeout = DEFAULT_TIMEOUT
    ...

Then, running tls_requests.settings.DEFAULT_TIMEOUT = 60.0 would take effect.

[thewebscraping]

@ytinyui
Thanks for asking!

For a general-purpose HTTP client — especially one used for external API calls or data scraping — a 30-second timeout is quite reasonable.

It’s long enough to handle slow responses or network latency, but not too long to leave hanging connections.

Of course, users can still override it via tls_requests.Client(timeout=...) depending on their use case (e.g., shorter for real-time APIs, longer for large file downloads).

So yes, I’d say 30.0s is a solid default.

[ytinyui]

Actually the timeout is just an example, what I want to change is DEFAULT_TLS_IDENTIFIER. Using the current default chrome_120 cannot bypass Cloudflare.

[thewebscraping]

Looks like your problem is cloudflare blocked. I will update the repo on monday, the idea is to add a rotator hook to rotate proxies, indentifiers and some other parameters. This allows mixing to change the fingerprint, hope it can help you.

[thewebscraping]

@ytinyui
please try new version. doc: https://thewebscraping.github.io/tls-requests/advanced/rotators/

[ytinyui]

It works perfectly, thanks!

[ytinyui]

It would be better if logging is used instead of printing to stdout in models/libraries.py.

[thewebscraping]

@ytinyui
That’s a great point — using logging instead of printing to stdout would be a good improvement. Feel free to open a new PR for that if you’d like!