T124365#2062088 documents the decision of the ArchCom RFC on API content versioning. Accordingly, OCG should add an Accept: header with the current Parsoid HTML version to your API requests for Parsoid HTML.
Description
Description
| Status | Assigned | Task | |
|---|---|---|---|
| · · · | |||
| Resolved | • GWicke | T128231 All known clients of Parsoid HTML (either directly hitting Parsoid or via RESTBase) should provide Accept: headers in their requests | |
| Resolved | cscott | T130685 OCG: Add Accept: header to your HTML requests to RESTBase/Parsoid as per T124365 | |
| · · · |
Event Timeline
Comment Actions
With the next version bump to 1.2.1, we took the opportunity to update the profile header to a valid url with documentation. Please use this instead if you haven't yet implemented this.
'text/html; charset=utf-8; profile="https://www.mediawiki.org/wiki/Specs/HTML/1.2.1"'
Comment Actions
Change 284356 had a related patch set uploaded (by Cscott):
Send Accept header to Parsoid/RESTBase to get data-mw attributes inline.
Comment Actions
Change 284356 merged by jenkins-bot:
Send Accept header to Parsoid/RESTBase to get data-mw attributes inline.
Comment Actions
Deployed. Can we verify that Parsoid is seeing the Accept header from OCG now, before I close this task?
Comment Actions
This goes to RESTBase and is not being passed into Parsoid yet, but I am going to mark this resolved. Can reopen if we see any problems once RB starts acting on these headers.