w3c / w3c/webdriver

Specify secure web proxy with a password

Open
#1,150 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
HTML
Stars
718
Forks
228
PR merge metrics
No merged PRs in 30d

Description

We would like to be able to specify a secure proxy, i.e. connection between browser and the proxy itself is secured by TLS. The proxy also needs to authenticate the browser with a password.

On Unix, this is possible by setting the following environment variables, depending on the destination's schema.

export http_proxy=https://user:pass@proxy.example.com:port  # for http destinations.
export https_proxy=https://user:pass@proxy.example.com:port  # for https destinations.

Some browsers allow PAC to specify the HTTPS proxy type to make use of the secure proxy, but PAC does not allow specifying passwords.

Currently, the W3C WebDriver recommendation only allows specifying httpProxy for http destinations and sslProxy for https destinations. It expects the proxy to speak plain HTTP without a password.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the W3C WebDriver recommendation's current httpProxy and sslProxy capability definitions, then compare them with the secure proxy and environment-variable examples in this issue. Done means the specification clearly defines secure proxy connections and password authentication for the relevant destination schemas.

Written by the indexing model from the issue text.

Assessment

Domain
networking
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.