Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Support pre-emptive Proxy Authentication for plaintext (http) requests

Open
#9,239 5 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
java, kotlin
Domain
networking

Research direction

Start by reading the mentioned createTunnelRequest logic and how authenticate handles proxy challenges. Clarify whether the requested work is pre-emptive Proxy-Authorization for plaintext HTTP, and establish the relevant standard behavior before proposing a change. Done means the expected behavior and scope are agreed, with tests covering the chosen HTTP proxy-authentication interaction.

Written by the indexing model from the issue text.

Description

bug

I want to use okhttp to implement --proxy-user so that the header includes Proxy-Authorization. I found that authenticate can achieve this, and it indeed works under HTTPS. However, once I send an HTTP request, like:

Request request = new Request.Builder()
.url("http://httpbin.org/headers") // This service returns the received request headers
.header("saaa", "bbb")
.build();
This header is not automatically added. I looked at the underlying source code and found that createTunnelRequest creates a fakeAuthChallengeResponse, which explains why it appears to be mandatory.

My first question is: Why isn't HTTP designed in the same way?
My second question is: After returning 407, HTTP also includes Proxy-Authorization. Is this interaction defined by a standard?

Thank you for your answer.

Dominant language
Kotlin
Stars
47.1k
Forks
9.3k
Avg merge
18h 18m
Merged PRs (30d)
15

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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.

More from lysine-dev/okhttp

All issues in lysine-dev/okhttp

Similar issues

More Kotlin issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.