Expose ClientSession defaults such as headers and auth for introspection

[mjpieters]

Long story short

Too many attributes of ClientSession are private without an explicit need to. The following constructor arguments can never be accessed after creating a session:

• headers
• skip_auto_headers
• auth
• json_serialize
• request_class
• response_class
• ws_response_class
• connector_owner
• raise_for_status
• timeout
• auto_decompress
• trust_env
• trace_configs

Expected behaviour

I want to be able to create a new session based on an existing session, only tweaking some aspects. Without access to these attributes, you can't properly create a new session instance with only some aspects replaced.

Actual behaviour

You have to access API private attribute to get at this information, making it much harder than necessary to create an updated wrapper as session needs change.

For example, I'm currently implementing an OAuth 2.0 authentication handler, which automatically fetches an authentication token if required for the current request, transparently. We create a client session in a different part of the app, shared between a group of objects, some of which need to dynamically switch to support OAuth 2.0.

Rather than have to create a new session for each of object regardless of OAuth needs (preventing connection re-use between some of these objects where the same server is involved) or having to introspect every request to see if OAuth applies to this specific request, I want to create a new session only when OAuth is actually needed, reusing the same connection pool, if and when OAuth is needed. But this requires knowing the headers, timeouts and trace config on the session used so far.

[asvetlov]

PR for providing properties for them is welcome, except request_class, response_class, and ws_response_class.

These three arguments will be removed soon.

[kornicameister]

What was the reason to hide them on first place? Perhaps exporting the API is not too cool. I have never needed that by making sessions persistent in one place and reusing whatever common bits I needed there.

Just asking, because not having them publicly available might have been done on purpose.

[asvetlov]

The reason for not exposing API was: nobody asked.
I had doubts what parameters should be exposed but now I see no objections.

[asvetlov]

#4193 adds a timeout property.
Looking for a champion for other names

[asvetlov]

No need to expose all properties at once, multiple PRs are acceptable.