Change Details

In T238849#5683035, @ssastry said that VE sends weak eTags in If-Match headers, which is a bug per the HTTP spec. To work around this, the ParsoidHandler base class disables conditional header handling - which isn't great, and we don't want to do this for core's page/{title}/html endpoint. The simples solution would be for VE to send strong eTags with If-Match (for If-None-Match, weak eTags are acceptable, though I'm not sure whether it would be correct here).

In T238849#5683035, @ssastry said that VE sends weak eTags in If-Match headers, which is a bug per the HTTP spec. To work around this, the ParsoidHandler base class disables conditional header handling - which isn't great, and we don't want to do this for core's page/{title}/html endpoint. The simples solution would be for VE to send strong eTags with If-Match (for If-None-Match, weak eTags are acceptable, though I'm not sure whether it would be correct here). The relevant code on the server side is ParsoidHandler::checkPreconditions. It should ideally be deleted, to restore the default behavior.

In T238849#5683035, @ssastry said that VE sends weak eTags in If-Match headers, which is a bug per the HTTP spec. To work around this, the ParsoidHandler base class disables conditional header handling - which isn't great, and we don't want to do this for core's page/{title}/html endpoint. The simples solution would be for VE to send strong eTags with If-Match (for If-None-Match, weak eTags are acceptable, though I'm not sure whether it would be correct here). The relevant code on the server side is ParsoidHandler::checkPreconditions. It should ideally be deleted, to restore the default behavior.