feat: HTTPS support for wda-client if webDriverAgentUrl is set #1042
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Currently the wda-client lib does not work with a WDA that is exposed over https. This is because the client does not properly set the scheme for the JWPProxy, when a remote WDA URL is provided.
mykola-mokhnach
approved these changes
Jul 9, 2025
KazuCocoa
approved these changes
Jul 10, 2025
github-actions bot
pushed a commit
that referenced
this pull request
Jul 10, 2025
## [9.15.0](v9.14.6...v9.15.0) (2025-07-10) ### Features * HTTPS support for wda-client if webDriverAgentUrl is set ([#1042](#1042)) ([f7c4193](f7c4193))
|
🎉 This PR is included in version 9.15.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Currently the wda-client lib does not work with a WDA that is exposed over https.
This is because the client does not properly set the scheme for the JWPProxy, when a remote WDA URL is provided.