Describe caching strategy for clients #79

Closed
opened 2025-12-28 17:36:03 +00:00 by sami · 2 comments
Owner

Originally created by @alexvanin on GitHub (Oct 24, 2022).

Originally assigned to: @KirillovDenis on GitHub.

HTTP Gateway does not define cache control headers, so it should be carefully done by proxy server. It should be mentioned in docs.

Originally created by @alexvanin on GitHub (Oct 24, 2022). Originally assigned to: @KirillovDenis on GitHub. HTTP Gateway does not define cache control headers, so it should be carefully done by proxy server. It should be mentioned in docs.
sami 2025-12-28 17:36:03 +00:00
Author
Owner

@alexvanin commented on GitHub (Oct 27, 2022):

Possible option: control caching on object attribute.

@alexvanin commented on GitHub (Oct 27, 2022): Possible option: control caching on object attribute.
Author
Owner

@alexvanin commented on GitHub (Oct 27, 2022):

Decided to mention in README that HTTP Gateway does not control caching. It is dependent on application use case and should be controlled by proxy.

@alexvanin commented on GitHub (Oct 27, 2022): Decided to mention in README that HTTP Gateway does not control caching. It is dependent on application use case and should be controlled by proxy.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
nspcc-dev/neofs-http-gw#79
No description provided.