webdriverio / webdriverio/webdriverio
bug: support for proxies not supported anymore when using native fetch
Open
Nobody has claimed this yet.
Bug 🐛
help wanted
- Dominant language
- TypeScript
- Stars
- 9.8k
- Forks
- 2.7k
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 69
Description
Discussed in https://github.com/webdriverio/webdriverio/discussions/13819
Originally posted by paussita22 October 28, 2024
Hi,
I'm trying to run GeoEdge proxy on a test that is using webdriverio and is running remotely in Selenium Grid but I'm not able to get it working, I try to pass the values in the capabilities of the browser but didn't work, wonder if you have some idea of what I'm missing?
proxy: {
proxyType: 'manual',
httpProxy: 'ip:port',
socksUsername: 'username',
socksPassword: 'pass',
sslProxy: 'ip:port',
},
```</div>Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with discussion 13819 and the native fetch proxy-handling entry point; the issue names no files or tests. Trace how the supplied proxy capabilities are handled for remote Selenium Grid sessions, then verify that the documented proxy configuration works with native fetch.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, typescript
- Domain
- networking, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100