Change Details

RESTBase clients count on ETags being provided to them with content. However, Parsoid/PHP does not emit ETags, which becomes a problem when clients are configured to use Parsoid directly (e.g. VE bypasses RESTBase for private wikis and calls Parsoid directly). Ideally, the ETag should be of the form `{revid}/{timeuuid}` to be compatible with what RESTBase emits.

RESTBase clients count on ETags being provided to them with content. However, Parsoid/PHP does not emit ETags, which becomes a problem when clients are configured to use Parsoid directly (e.g. VE bypasses RESTBase for private wikis and calls Parsoid directly). Ideally, the ETag should be of the form `{revid}/{timeuuid}` to be compatible with what RESTBase emits. See also {T235462}

RESTBase clients count on ETags being provided to them with content. However, Parsoid/PHP does not emit ETags, which becomes a problem when clients are configured to use Parsoid directly (e.g. VE bypasses RESTBase for private wikis and calls Parsoid directly). Ideally, the ETag should be of the form `{revid}/{timeuuid}` to be compatible with what RESTBase emits. See also {T235462}