Page MenuHomePhabricator

Provide page cache timestamp as JavaScript variable
Closed, ResolvedPublic


Author: gangleri


It might be a good ides to expand the "final comment" before </body></html>
with additional information:
revisionid; it should be available in the browsers sorce code anyway
timestamp; I suppose the timestamp when this page gets generated / cached

I assume this would facilitate referencing and fault finding.

best regards reinhardt [[user:gangleri]]

Version: unspecified
Severity: enhancement



Event Timeline

bzimport raised the priority of this task from to Medium.Nov 21 2014, 9:10 PM
bzimport set Reference to bz5498.
bzimport added a subscriber: Unknown Object (MLST).

It would be far more useful to provide that in
machine-readable form for JS usage.

gangleri wrote:

(In reply to comment #1)

It would be far more useful to provide that in
machine-readable form for JS usage.

Agree. Start with the machine-readable form for JS usage. If it is to cryptic
(if people could not associate it with its meaning) then please append a comment
character and a minimal legible hint.

gangleri wrote:

I wonder how action=purge effects should be included.

User A describes the rendering of page X with revision_id N at (UTC) time NOW.
Templates might change, software updates might be involved, action=purge migth
generate different code.

If user B looks at page X with revision_id N at (UTC) time LATER he should be
able to see at least the timestamp of last *rebuild* of the page. This timestamp
may differ from the timestamp of the last change for page X.

Please stop posting random junk all over bug reports. Thanks.

robchur wrote:

The revision identifier is exposed as wgCurRevisionId. I'm not sure we need the
"page touched" timestamp...

robchur wrote:

Original issue was fixed, the page_touched value would be of limited use to client-side scripts.