Change Details

If Parsoid/PHP gets a html2wt request with a data-parsoid blob generated by Parsoid/JS, we should reject it since we will severely corrupt the page if it went through given that Parsoid/PHP use byte offsets for data-parsoid and Parsoid/JS uses ucs2 offsets. Fortunately, the fix for {T222738} adds annotations to the data-parsoid blob which makes this detection simple.

If Parsoid/PHP gets a html2wt request with a data-parsoid blob generated by Parsoid/JS, we should reject it since we will severely corrupt the page if it went through given that Parsoid/PHP use byte offsets for data-parsoid and Parsoid/JS uses ucs2 offsets. Fortunately, the fix for {T222738} adds annotations to the data-parsoid blob which makes this detection simple. HTTP 421 (Misdirected request) seems like the appropriate response in this case allowing RESTBase to retry with a request to Parsoid/JS instead.

If Parsoid/PHP gets a html2wt request with a data-parsoid blob generated by Parsoid/JS, we should reject it since we will severely corrupt the page if it went through given that Parsoid/PHP use byte offsets for data-parsoid and Parsoid/JS uses ucs2 offsets. Fortunately, the fix for {T222738} adds annotations to the data-parsoid blob which makes this detection simple. HTTP 421 (Misdirected request) seems like the appropriate response in this case allowing RESTBase to retry with a request to Parsoid/JS instead.