Skip to content

Conversation

Mantisus
Copy link
Collaborator

Description

  • fix for passing verify to transport in HttpxHttpClient

Issues

Checklist

  • CI passed

@Mantisus
Copy link
Collaborator Author

Since we all agree that we're not ready to add custom transport support #801, I think this PR is ready for review in its current form.

@Mantisus Mantisus marked this pull request as ready for review December 11, 2024 15:06
ignore_http_error_status_codes: Iterable[int] = (),
http1: bool = True,
http2: bool = True,
verify: str | bool | SSLContext = True,
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I know that this is the name of the attribute in httpx, but maybe we could rename this to something like verify_certificates or verify_ssl for better clarity?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These names are indeed clearer.

But as a weak argument. The requests API, has become such a standard for HTTP clients in Python that any Python developer, will expect exactly verify.

@Mantisus Mantisus self-assigned this Dec 12, 2024
@Mantisus Mantisus requested a review from janbuchar December 13, 2024 13:20
@janbuchar janbuchar merged commit 074d083 into apify:master Dec 13, 2024
23 checks passed
@vdusek vdusek added the t-tooling Issues with this label are in the ownership of the tooling team. label Dec 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
t-tooling Issues with this label are in the ownership of the tooling team.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

HTTPX verify field is not being propagated
3 participants