Skip to content

Conversation

seanbudd
Copy link
Member

Link to issue number:

Reimplements #18354
Reimplements #18490
Reimplements #18402

Summary of the issue:

Description of user facing changes:

Description of developer facing changes:

Description of development approach:

Testing strategy:

Known issues with pull request:

Code Review Checklist:

  • Documentation:
    • Change log entry
    • User Documentation
    • Developer / Technical Documentation
    • Context sensitive help for GUI changes
  • Testing:
    • Unit tests
    • System (end to end) tests
    • Manual testing
  • UX of all users considered:
    • Speech
    • Braille
    • Low Vision
    • Different web browsers
    • Localization in other languages / culture than English
  • API is compatible with existing add-ons.
  • Security precautions taken.

@coderabbitai summary

hdzrvcc0X74 and others added 4 commits July 22, 2025 09:34
### Reverts PR
Reverts #18354
Reverts #18490
Reverts #18402

### Issues fixed
<!-- Issues that will be closed by reverting, i.e. the issues introduced
via the PR getting reverted -->
Fixes #18519 

### Issues reopened
<!-- Issues that will be re-opened by reverting, i.e. the issues that
were fixed via the PR getting reverted -->
Reopens #15905

### Reason for revert
The current implementation breaks NVDA remote and breaks add-on APIs

### Can this PR be reimplemented? If so, what is required for the next
attempt
- use truststore.SSLContext directly rather than source code wide
injections. It is
[unclear](https://truststore.readthedocs.io/en/latest/#using-truststore-with-requests)
how to do that with requests. [this SO answer suggestions an
option](https://stackoverflow.com/a/78265028).
- perform the changes in an API breaking release, encourage authors to
use `inject_into_ssl, extract_from_ssl` where required
@CyrilleB79
Copy link
Contributor

I do not know if it is still applicable or not. But if yes, please check that DEBUGWARNING's are not replaced in the log by VERBOSE's. See #18402 (comment) for more details.

@seanbudd seanbudd added conceptApproved Similar 'triaged' for issues, PR accepted in theory, implementation needs review. api-breaking-change labels Jul 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api-breaking-change conceptApproved Similar 'triaged' for issues, PR accepted in theory, implementation needs review.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants