Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request includes several changes to the TLS settings and introduces a new Chrome version (v133) with specific configurations. The most important changes are grouped by theme below:
TLS Settings Enhancements:
alps_use_new_codepoint
to theChromeTlsSettings
andHttpsLayerSettings
structs to support the new ALPS codepoint. [1] [2]alps_protos
method inConnectConfigurationExt
to accept the new ALPS codepoint parameter. [1] [2]HttpsLayer
andBoringTlsConnector
implementations to use the newalps_use_new_codepoint
field. [1] [2]Chrome v133 Configuration:
permute_extensions
,pre_shared_key
, andalps_use_new_codepoint
.Impersonate
enum andImpersonateBuilder
settings. [1] [2]mod_generator
entry for Chrome v133 with specific user-agent strings for different platforms.Code Refactoring:
AlpsProtos
struct to simplify the code.These changes enhance the flexibility and functionality of the TLS settings, especially with the introduction of the new ALPS codepoint, and add support for a new Chrome version with specific configurations.