Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Set out rules for cache-friendly conditional requests #107

Open
jfuerth opened this issue Mar 5, 2021 · 2 comments
Open

Set out rules for cache-friendly conditional requests #107

jfuerth opened this issue Mar 5, 2021 · 2 comments
Labels
feature New feature or request

Comments

@jfuerth
Copy link
Contributor

jfuerth commented Mar 5, 2021

This issue arose out of the discussion in #98.

The Search spec should reference the HTTP specification to say that servers MAY implement conditional HTTP requests using the standard (eTag/If-Match and Date/If-Modified-Since) headers to help clients take advantage of the built-in caching behaviour of HTTP.

@ifokkema
Copy link

I think this is a great suggestion. I suppose the idea is that we can hack ETags here and say, e.g.:

Request:

GET /tables/variants.hg19/data
If-Match: "data_license=cc_by_4.0"
...

Reply:

HTTP 200 OK
ETag: "data_license=cc_by_4.0"
...
<data>

@mcupak mcupak modified the milestones: 1.0.0, 1.1.0 Apr 14, 2021
@mcupak mcupak removed this from the 1.1.0 milestone May 26, 2021
@mcupak mcupak added the feature New feature or request label May 26, 2021
@mcupak mcupak added this to the 1.1.0 milestone May 26, 2021
@ifokkema
Copy link

ifokkema commented Jul 9, 2021

While implementing this in LOVD3 (LOVDnl/LOVD3#518), I realized:

(...) and Date/If-Modified-Since) headers (...)

This should be Last-Modified / If-Modified-Since.

@mcupak mcupak removed this from the 1.1.0 milestone Dec 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants