| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
chains (#3)
* Squashed 'vendor/src/github.com/alexedwards/stack/' content from commit a4c0268
git-subtree-dir: vendor/src/github.com/alexedwards/stack
git-subtree-split: a4c0268505f12934376d6d8fdca232416861e271
* Use context-aware handler chains to limit repeated handling
Presently each middleware must advance through the handler chain to
reach the router endpoint. In the case of multiple compressors (gzip,
deflate) we need to be able to walk through the chain without additional
processing of already handled requests. This implements some simple
iteration logic based on request context that we pass down the chain.
Signed-off-by: Paul Mundt <paul.mundt@adaptant.io>
|
| | |
|
| |\
| |
| |
| | |
pmundt-deflate
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
This enables optional support for deflate compression to be used for
HTTP requests. Primarily useful in cases where gzip compression is not
available on the requesting client side.
|
| |/
|
|
|
|
|
| |
In the case where the server has enabled gzip support but it is not
supported by the requesting client, the error path serves up the
uncompressed response but then fails to return immediately, resulting in
the compressed response being written out also.
|
| | |
|
| | |
|
| | |
|
|
|
Only 'define' is currently working so far.
|
