Packages

  • package root
    Definition Classes
    root
  • package org
    Definition Classes
    root
  • package http4s
    Definition Classes
    org
  • package client

    Provides extension methods for using the a http4s org.http4s.client.Client

    Provides extension methods for using the a http4s org.http4s.client.Client

    import scalaz.concurrent.Task
import org.http4s._
import org.http4s.client._
import org.http4s.Http4s._
import org.http4s.Status._
import org.http4s.Method._
import org.http4s.EntityDecoder

def client: Client = ???

val r: Task[String] = client(GET(uri("https://www.foo.bar/"))).as[String]
val r2: DecodeResult[String] = client(GET(uri("https://www.foo.bar/"))).attemptAs[String] // implicitly resolve the decoder
val req1 = r.run
val req2 = r.run // Each invocation fetches a new Result based on the behavior of the Client
    Definition Classes
    http4s
  • package asynchttpclient
    Definition Classes
    client
  • package blaze
    Definition Classes
    client
  • package impl
    Definition Classes
    client
  • package middleware
    Definition Classes
    client
  • FollowRedirect
  • Retry
  • RetryPolicy
  • package oauth1

    Basic OAuth1 message signing support

    Basic OAuth1 message signing support

    This feature is not considered stable.

    Definition Classes
    client
p

org.http4s.client

middleware

package middleware

Ordering
  1. Alphabetic
Visibility
  1. Public
  2. All

Value Members

  1. object FollowRedirect

    Client middleware to follow redirect responses.

    Client middleware to follow redirect responses.

    A 301 or 302 response is followed by: - a GET if the request was GET or POST - a HEAD if the request was a HEAD - the original request method and body if the body had no effects - the redirect is not followed otherwise

    A 303 response is followed by: - a HEAD if the request was a HEAD - a GET for all other methods

    A 307 or 308 response is followed by: - the original request method and body, if the body had no effects - the redirect is not followed otherwise

    Whenever we follow with a GET or HEAD, an empty body is sent, and all payload headers defined in https://tools.ietf.org/html/rfc7231#section-3.3 are stripped.

    If the response does not contain a valid Location header, the redirect is not followed.

  2. object Retry
  3. object RetryPolicy

Ungrouped