I don't think we currently error if the user specifices a content-length header and then writes more bytes to the response. I think this is something we could detect and error. Some http clients have a hard time handling this case (especially with pipelining) and would be nice if we could help with reducing the probability of this occuring.

It may be a specific request but since there is a zip file handler for Android, doesn't hurt to ask for a desktop (maybe multiple backends?) implementation.

I would like to try that in the future but if anyone has time before feel free to do it.

Similar

See original issue and associated discussion in Node.js issue tracker here: nodejs/node#36158

/cc @asklar, @aduh95, @bzoz

Support using="-android viewmatcher", value="<JSON>"

appium/appium-espresso-driver#516

like appium/appium#12372

Acceptance Criteria:

• Ruby
• Python
• Java
• C#
• WebdriverIO ?
• wd ?