Change Details

For language variants support #parsoid will be the ultimate source of truth regarding whether a certain page can or can not be affected by language variant, so for those pages that can possibly be transformed, #parsoid will set `vary: accept-language` in it's response. RESTBase will proxy and store that for HTML content, but for MCS #restbase doesn't want to also fetch in #parsoid HTML in order to determine whether to set the header. So MCS, when requesting HTML content for transformation should just proxy and return the Vary header it got together with HTML.

MCS should return the same `vary` header as it got when requesting #parsoid HTML. For language variants support #parsoid will be the ultimate source of truth regarding whether a certain page can or can not be affected by language variant, so for those pages that can possibly be transformed, #parsoid will set `vary: accept-language` in its response. RESTBase will proxy and store that for HTML content, but for MCS #restbase doesn't want to also fetch in #parsoid HTML in order to determine whether to set the header. So MCS, when requesting HTML content for transformation should just proxy and return the `Vary` header it got together with HTML.

MCS should return the same `vary` header as it got when requesting #parsoid HTML. For language variants support #parsoid will be the ultimate source of truth regarding whether a certain page can or can not be affected by language variant, so for those pages that can possibly be transformed, #parsoid will set `vary: accept-language` in it'its response. RESTBase will proxy and store that for HTML content, but for MCS #restbase doesn't want to also fetch in #parsoid HTML in order to determine whether to set the header. So MCS, when requesting HTML content for transformation should just proxy and return the `Vary` header it got together with HTML.