@tusbar/cache-control
Advanced tools
Comparing version 0.2.0 to 0.2.1
{ | ||
"name": "@tusbar/cache-control", | ||
"public": true, | ||
"version": "0.2.0", | ||
"version": "0.2.1", | ||
"description": "Format and parse HTTP Cache-Control header", | ||
@@ -10,2 +10,7 @@ "main": "index.js", | ||
}, | ||
"keywords": [ | ||
"cache-control", | ||
"http", | ||
"rfc7234" | ||
], | ||
"repository": "https://github.com/tusbar/cache-control", | ||
@@ -12,0 +17,0 @@ "author": "Bertrand Marron <bertrand.marron@gmail.com>", |
@@ -20,3 +20,3 @@ # cache-control [![CircleCI](https://circleci.com/gh/tusbar/cache-control.svg?style=svg)](https://circleci.com/gh/tusbar/cache-control) | ||
### parse(header) | ||
### `parse(header)` | ||
@@ -49,3 +49,3 @@ ```js | ||
### format(cacheControl) | ||
### `format(cacheControl)` | ||
@@ -73,4 +73,16 @@ ```js | ||
## FAQ | ||
**Why another cache-control library?** | ||
None of the existing libraries focus on just parsing the `Cache-Control` headers. There are some that expose Express (or connect-like) middlewares, and some unmaintained other ones that do rudimentary parsing of the header. The idea of this module is to parse the header according to the RFC with no further analysis or integration. | ||
## See also | ||
- [`cachecontrol`](https://github.com/pquerna/cachecontrol): Golang HTTP Cache-Control Parser and Interpretation | ||
## License | ||
MIT |
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
152060
86