memcached

README

Memcached http provider

Publishes challenges into memcached where they can be retrieved by nginx. Allows specifying multiple memcached servers and the responses will be published to all of them, making it easier to verify when your domain is hosted on a cluster of servers.

Example nginx config:

    location /.well-known/acme-challenge/ {
        set $memcached_key "$uri";
        memcached_pass 127.0.0.1:11211;
    }

Documentation

Overview

Package memcached implements a HTTP provider for solving the HTTP-01 challenge using memcached in combination with a webserver.

Index

• type HTTPProvider
  • func NewMemcachedProvider(hosts []string) (*HTTPProvider, error)
  • func (w *HTTPProvider) CleanUp(domain, token, keyAuth string) error
  • func (w *HTTPProvider) Present(domain, token, keyAuth string) error

Types

type HTTPProvider

type HTTPProvider struct {
	// contains filtered or unexported fields
}

HTTPProvider implements HTTPProvider for `http-01` challenge

func NewMemcachedProvider

func NewMemcachedProvider(hosts []string) (*HTTPProvider, error)

NewMemcachedProvider returns a HTTPProvider instance with a configured webroot path

func (*HTTPProvider) CleanUp

func (w *HTTPProvider) CleanUp(domain, token, keyAuth string) error

CleanUp removes the file created for the challenge

func (*HTTPProvider) Present

func (w *HTTPProvider) Present(domain, token, keyAuth string) error

Present makes the token available at `HTTP01ChallengePath(token)` by creating a file in the given webroot path