Skip to content
This repository has been archived by the owner on Mar 28, 2019. It is now read-only.

Deactivate Cache Headers when Authenticated. #449

Closed
Natim opened this issue Sep 11, 2015 · 2 comments
Closed

Deactivate Cache Headers when Authenticated. #449

Natim opened this issue Sep 11, 2015 · 2 comments
Assignees

Comments

@Natim
Copy link
Contributor

Natim commented Sep 11, 2015

When updating a collection, we should disable cache headers.

@leplatrem
Copy link
Contributor

Regarding single record updates (PATCH/PUT), the response body will return the last version of the records.

So naively I would say that it concerns the GET record more than the collection.

Could you explain why you thought of collection specifically?

@Natim
Copy link
Contributor Author

Natim commented Sep 16, 2015

I suspect that when using KWAC to update the collection it can be difficult to sync your local records against a cached collection because each time you will call the sync you may get cached values.
Also if the _since changed inbetween, it will probably re-cache correctly but not necessarily with the right values for the public.

We may delay this until we see a problem to update cached collection but we should start thinking about problems when updating cached-collections.

@leplatrem leplatrem self-assigned this Oct 28, 2015
Natim added a commit that referenced this issue Oct 29, 2015
…enticated

Set cache headers only when anonymous (fixes #449)
glasserc pushed a commit that referenced this issue May 20, 2016
Add uwsgi bind error to troubleshooting (fixes #447)
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants