After deploying content negotiation and Parsoid 2.0, MCS should request 2.0 Parsoid HTML in it's Accept header. This should be done sooner rather than later, cause now all requests from MCS to RESTBase during updates require downgrading, so background update latency increased by 200 ms on average.
Description
Description
Details
Details
Related Changes in Gerrit:
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| Request Parsoid HTML 2.0.0, not 1.7.0 | mediawiki/services/mobileapps | master | +1 -1 |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | • Pchelolo | T205935 MCS should request 2.0 Parsoid HTML | |||
| Resolved | • Pchelolo | T128040 Document and implement the REST API format versioning and negotiation policy | |||
| Open | None | T114413 Support various conversions in Parsoid's pb2pb endpoint | |||
| Resolved | Arlolra | T202666 html2wt endpoint should handle mismatching content versions | |||
| Resolved | • Pchelolo | T202682 Improve Accept header normalization in VCL for REST API |
Event Timeline
Comment Actions
Change 463866 had a related patch set uploaded (by Jforrester; owner: Jforrester):
[mediawiki/services/mobileapps@master] Request Parsoid HTML 2.0.0, not 1.7.0
Comment Actions
Just to be clear, should this be done now, or does something need to be deployed in Parsoid and/or RESTBase first? I see there's a new HTML 2.0.0 spec as of yesterday, but don't see any references in the commit logs.
Comment Actions
@Mholloway Everything is deployed in both RB and Parsoid, but let's wait till tomorrow for MCS deployment in case we need to rollback?
Comment Actions
Change 463866 merged by jenkins-bot:
[mediawiki/services/mobileapps@master] Request Parsoid HTML 2.0.0, not 1.7.0
Comment Actions
Beautiful. Look at the update latency impact!
Resolving. Thank you @Mholloway for testing and getting it out so quickly.