Timeline for Command line tool to check when a URL was updated?
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 4, 2022 at 16:51 | answer | added | ahmetpergamum | timeline score: 0 | |
| Dec 5, 2015 at 18:23 | answer | added | nwk | timeline score: 3 | |
| Dec 5, 2015 at 17:07 | vote | accept | Scott Deerwester | ||
| Dec 5, 2015 at 1:10 | comment | added | Scott Deerwester | That's true enough. My particular use case is to monitor Web-based downloads of databases, so that's less of an issue. Still something to be mindful of, though. | |
| Dec 5, 2015 at 0:49 | comment | added | cas | Note, though, that Last-Modified headers are completely useless on many sites because the pages are generated dynamically from a database and will always return a LM header of approximately now. This is often done deliberately as a cache-busting technique and to force re-fetches (and thus marketable page views) when the client requests the page with an If-Modified-Since request header. | |
| Dec 4, 2015 at 23:26 | answer | added | RobertL | timeline score: 4 | |
| Dec 4, 2015 at 23:12 | answer | added | Scott Deerwester | timeline score: 1 | |
| Dec 4, 2015 at 22:26 | comment | added | iruvar | curl --head url seems to report the headers to me. Assuming a Last-Modified header does come through, curl --header url | awk '/Last-Modified/{print $2}' should be able to extract the value | |
| Dec 4, 2015 at 22:02 | history | asked | Scott Deerwester | CC BY-SA 3.0 |