akka/akka-http

High-level HTTP client support

Open

#113 opened on Sep 8, 2016

View on GitHub
 (13 comments) (3 reactions) (0 assignees)Scala (598 forks)batch import
1 - triagedhelp wantedt:client

Repository metrics

Stars
 (1,311 stars)
PR merge metrics
 (Avg merge 1d 10h) (2 merged PRs in 30d)

Description

Issue by jrudolph Wednesday Feb 11, 2015 at 13:54 GMT Originally opened as https://github.com/akka/akka/issues/16856

It would be convenient if akka-http would provide common high-level HTTP functionality similar to what a browser supports in its backend. This is a collection of all the things that would belong into this category. This is a metaticket and each subfeature has its own ticket.

  • connection pooling and configurable request queuing (provided by host-level API #15681)
  • request-level API (#15906)
  • automatic redirection (#15990)
  • automatic retry attempts (#16852)
  • try different IP addresses on retries (#16827)
  • HTTP proxy support (for HTTP: #16853, for HTTPS: #16153)
  • authentication data store (#16854)
  • cookie store (#16855)
  • response routing DSL (#15909)
  • request building should be polished and documented (https://github.com/akka/akka/issues/18550)
  • optional: response decompression (https://github.com/akka/akka/issues/16813)
  • optional: Add support for OAuth authentication #16857

Contributor guide

Research direction
This is a meta issue; consider picking one of the sub features such as 'connection pooling' or 'automatic redirection' and implement it. Start by understanding the existing host level API structure.
Tech stack
None
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Scalaakka http
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20