Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow a custom context key #65

Merged
merged 2 commits into from
Dec 11, 2019
Merged

Allow a custom context key #65

merged 2 commits into from
Dec 11, 2019

Conversation

dtomcej
Copy link
Contributor

@dtomcej dtomcej commented Dec 10, 2019

This PR:

  • Allows for a custom context key to be set

This allows each instance of secure to manage its own headers, and work independently of any others.

Allows chaining secure instances, so that options only have to be set for each link in the chain, instead of for the final result.

Fixes #64

@unrolled
Copy link
Owner

Looks great, thanks for the PR!

@unrolled unrolled merged commit d301013 into unrolled:v1 Dec 11, 2019
@unrolled
Copy link
Owner

unrolled commented Dec 11, 2019

Tagged as v1.0.7

@dtomcej
Copy link
Contributor Author

dtomcej commented Dec 11, 2019

Sweeet thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Static SecureHeaderKey does not allow multiple instances
2 participants