Skip to content
This repository has been archived by the owner on Sep 18, 2021. It is now read-only.

Configurable Cache Control for Discovery Endpoints #3751

Open
wants to merge 1 commit into
base: dev
Choose a base branch
from

Conversation

gnjack
Copy link

@gnjack gnjack commented Jun 21, 2017

Adds feature requested for IdentityServer4 in IdentityServer/IdentityServer4#810 but this time for IdentityServer3

It would be nice if there was a supported way to define cache headers for the discovery endpoint. Right now, our resource servers assume that the jwk immediately expires if there is no cache header set.

Add DiscoveryOptions.ClientCacheInterval to set the maxage cache control header on the discovery endpoints. Defaults to one hour.

This gives clients a hint how often they should refresh their cached copy of the discovery document.

Feature implemented in a similar manner to IdentityServer4 IdentityServer/IdentityServer4@58e6c3a

…rol header on the discovery endpoints. Defaults to one hour.

This gives clients a hint how often they should refresh their cached copy of the discovery document.
@ghost ghost removed the cla-already-signed label Dec 7, 2017
@ghost ghost deleted a comment from dnfclas Dec 7, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants