forked from TrueCloudLab/frostfs-http-gw
[#215] Mention caching strategy in README.md
Signed-off-by: Denis Kirillov <denis@nspcc.ru>
This commit is contained in:
parent
ef0c17372f
commit
4a0188b8f9
1 changed files with 5 additions and 0 deletions
|
@ -376,6 +376,11 @@ set of reply headers generated using the following rules:
|
||||||
if they can be safely represented in HTTP header), for example `FileName`
|
if they can be safely represented in HTTP header), for example `FileName`
|
||||||
attribute becomes `X-Attribute-FileName` header
|
attribute becomes `X-Attribute-FileName` header
|
||||||
|
|
||||||
|
##### Caching strategy
|
||||||
|
|
||||||
|
HTTP Gateway doesn't control caching (doesn't anything with the `Cache-Control` header). Caching strategy strictly
|
||||||
|
depends on application use case. So it should be carefully done by proxy server.
|
||||||
|
|
||||||
### Uploading
|
### Uploading
|
||||||
|
|
||||||
You can POST files to `/upload/$CID` path where `$CID` is a container ID or its name if NNS is enabled. The
|
You can POST files to `/upload/$CID` path where `$CID` is a container ID or its name if NNS is enabled. The
|
||||||
|
|
Loading…
Reference in a new issue