Use custom SSL context to avoid 403's from Cloudflare#72
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| super().__init__(*args, **kwargs) | ||
|
|
||
| self.name = name | ||
| self.verify = verify |
There was a problem hiding this comment.
The new verify parameter defaults to a custom SSL context, but super().__init__(*args, **kwargs) is called without verify, and the subsequent self.verify = verify assignment does not reconfigure the already-created transport in httpx. As a result, requests made by this client will still use the default TLS configuration, so the Cloudflare-bypass change has no effect when the client is constructed without an explicit verify kwarg. This matters whenever you rely on the custom TLS fingerprint to avoid 403s.
Useful? React with 👍 / 👎.
| homepage = "https://mottle.it" | ||
| repository = "https://github.com/Ch00k/mottle" | ||
| requires-python = ">=3.12,<3.13" | ||
| requires-python = ">=3.14" |
There was a problem hiding this comment.
The project now declares requires-python = ">=3.14", but the Dockerfile still builds on python3.12 for both builder and runtime (Dockerfile:1,19). That combination causes uv sync/pip to reject the project during image builds, so the container will fail to build in current environments. Unless the base images are updated to 3.14, this requirement bump breaks deployments.
Useful? React with 👍 / 👎.
1 participant
No description provided.