swift-server / swift-server/async-http-client

Support for requesting/using connections that don't come out of the connection pool

Open
#354 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Swift
Stars
1.1k
Forks
156
PR merge metrics
No merged PRs in 30d

Description

In some cases we need more control over which connections are used and must prevent that connections are used for other requests outside of a certain context. An example of this is NTLM authentication which is connection based, which requires a negotiation request immediately before each authenticated request to happen on the same connection.

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

No files, tests, or entry points are identified in the issue. Start by locating the connection-pool and request-execution paths, then clarify the API and tests needed to reserve a connection for a negotiation/authenticated request pair without sharing it with other requests.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.