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

Use metadata keys last-modified and etag #109

Closed
jnioche opened this issue Mar 12, 2015 · 1 comment
Closed

Use metadata keys last-modified and etag #109

jnioche opened this issue Mar 12, 2015 · 1 comment
Assignees
Labels
Milestone

Comments

@jnioche
Copy link
Contributor

jnioche commented Mar 12, 2015

Allow their use globally via configuration as well as overriding the de/activation on a per URL basis with use.Etag or use.ModifiedSince.

@jnioche jnioche mentioned this issue Mar 13, 2015
@jnioche jnioche modified the milestone: 0.5 Mar 13, 2015
@jnioche jnioche self-assigned this Mar 13, 2015
@jnioche jnioche removed this from the 0.5 milestone Apr 8, 2015
@jnioche jnioche added the core label Jul 4, 2016
@jnioche jnioche added this to the 1.0 milestone Jul 4, 2016
@jnioche jnioche changed the title Use metadata keys last-modified and tag Use metadata keys last-modified and etag Jul 4, 2016
@jnioche jnioche closed this as completed in 53749f5 Jul 4, 2016
@jnioche
Copy link
Contributor Author

jnioche commented Jul 4, 2016

To use etag and last-modified, you now just need to specify

 metadata.persist:
   - etag
   - last-modified

in the crawl configuration. This way, the key values will be persisted if returned by the server and used the next time round when querying it.

This can also be set on a per URL basis by setting the K/V in the metadata.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant