middleware/cache/item_test.go

package cache

import (
	"testing"

	"github.com/miekg/dns"
)

func TestKey(t *testing.T) {
	if x := rawKey("miek.nl.", dns.TypeMX, false); x != "0miek.nl..15" {
		t.Errorf("failed to create correct key, got %s", x)
	}
	if x := rawKey("miek.nl.", dns.TypeMX, true); x != "1miek.nl..15" {
		t.Errorf("failed to create correct key, got %s", x)
	}
	// rawKey does not lowercase.
	if x := rawKey("miEK.nL.", dns.TypeMX, true); x != "1miEK.nL..15" {
		t.Errorf("failed to create correct key, got %s", x)
	}
}
Cache (#126) * Add middleware/cache Add a caching middleware that caches nxdomain, nodata and successful responses. It differentiates between DNSSEC on normal DNS replies. Each reply is compress and scrubbed so it will fit the specific client asking for it. * first simple test, less exporting of stuff * more * Add middleware/cache Add a caching middleware that caches nxdomain, nodata and successful responses. It differentiates between DNSSEC on normal DNS replies. Each reply is compressed and scrubbed so it will fit the specific client asking for it. The TTL is decremented with the time spend in the cache. There is syntax that allows you to cap the TTL for all records, no matter what. This allows for a shortlived cache, just to absorb query peaks. +Tests * cache test infrastructure * Testing 2016-04-19 11:13:24 +01:00			`package cache`

			`import (`
			`"testing"`

			`"github.com/miekg/dns"`
			`)`

			`func TestKey(t *testing.T) {`
middleware/cache: split cache in positive and negative and use lru (#298) Make the cache memory bounded, by using a LRU cache. Also split the cache in a positive and negative one - each with its own controls. Extend the cache stanza to allow for this: cache { positive limit [ttl] negative limit [ttl] } is now possible. This also add a cache_test.go in the toplevel test/ directory that exercises the caching path. Fixes #260 2016-10-02 08:31:44 +01:00			`if x := rawKey("miek.nl.", dns.TypeMX, false); x != "0miek.nl..15" {`
			`t.Errorf("failed to create correct key, got %s", x)`
Cache (#126) * Add middleware/cache Add a caching middleware that caches nxdomain, nodata and successful responses. It differentiates between DNSSEC on normal DNS replies. Each reply is compress and scrubbed so it will fit the specific client asking for it. * first simple test, less exporting of stuff * more * Add middleware/cache Add a caching middleware that caches nxdomain, nodata and successful responses. It differentiates between DNSSEC on normal DNS replies. Each reply is compressed and scrubbed so it will fit the specific client asking for it. The TTL is decremented with the time spend in the cache. There is syntax that allows you to cap the TTL for all records, no matter what. This allows for a shortlived cache, just to absorb query peaks. +Tests * cache test infrastructure * Testing 2016-04-19 11:13:24 +01:00			`}`
middleware/cache: split cache in positive and negative and use lru (#298) Make the cache memory bounded, by using a LRU cache. Also split the cache in a positive and negative one - each with its own controls. Extend the cache stanza to allow for this: cache { positive limit [ttl] negative limit [ttl] } is now possible. This also add a cache_test.go in the toplevel test/ directory that exercises the caching path. Fixes #260 2016-10-02 08:31:44 +01:00			`if x := rawKey("miek.nl.", dns.TypeMX, true); x != "1miek.nl..15" {`
			`t.Errorf("failed to create correct key, got %s", x)`
Cache (#126) * Add middleware/cache Add a caching middleware that caches nxdomain, nodata and successful responses. It differentiates between DNSSEC on normal DNS replies. Each reply is compress and scrubbed so it will fit the specific client asking for it. * first simple test, less exporting of stuff * more * Add middleware/cache Add a caching middleware that caches nxdomain, nodata and successful responses. It differentiates between DNSSEC on normal DNS replies. Each reply is compressed and scrubbed so it will fit the specific client asking for it. The TTL is decremented with the time spend in the cache. There is syntax that allows you to cap the TTL for all records, no matter what. This allows for a shortlived cache, just to absorb query peaks. +Tests * cache test infrastructure * Testing 2016-04-19 11:13:24 +01:00			`}`
middleware/cache: split cache in positive and negative and use lru (#298) Make the cache memory bounded, by using a LRU cache. Also split the cache in a positive and negative one - each with its own controls. Extend the cache stanza to allow for this: cache { positive limit [ttl] negative limit [ttl] } is now possible. This also add a cache_test.go in the toplevel test/ directory that exercises the caching path. Fixes #260 2016-10-02 08:31:44 +01:00			`// rawKey does not lowercase.`
			`if x := rawKey("miEK.nL.", dns.TypeMX, true); x != "1miEK.nL..15" {`
			`t.Errorf("failed to create correct key, got %s", x)`
Cache (#126) * Add middleware/cache Add a caching middleware that caches nxdomain, nodata and successful responses. It differentiates between DNSSEC on normal DNS replies. Each reply is compress and scrubbed so it will fit the specific client asking for it. * first simple test, less exporting of stuff * more * Add middleware/cache Add a caching middleware that caches nxdomain, nodata and successful responses. It differentiates between DNSSEC on normal DNS replies. Each reply is compressed and scrubbed so it will fit the specific client asking for it. The TTL is decremented with the time spend in the cache. There is syntax that allows you to cap the TTL for all records, no matter what. This allows for a shortlived cache, just to absorb query peaks. +Tests * cache test infrastructure * Testing 2016-04-19 11:13:24 +01:00			`}`
			`}`