Skip to main content

MTE Relay web client v4.5.3: Firefox request body fix

· 2 min read
Trevor Blackman
Trevor Blackman
Engineering Director

mte-relay-browser-public-client 4.5.3 is a patch release of the v4 web client. In Firefox, every earlier v4 client sent request bodies as empty. Chrome and Edge were not affected. The relay needs no change, and 4.5.3 works with every v4 server.

Fixed​

  • POST, PUT and PATCH requests sent with mteFetch from Firefox now carry their body. Before 4.5.3 they reached the relay with no body, and the relay forwarded an empty body to your API. JSON endpoints usually answered 400 Bad Request. An endpoint that accepts an empty body could have stored a write with no data.
  • The client decided whether a request had a body by checking Request.body. Firefox does not implement Request.body, so that check always failed there. The client now reads the request bytes directly.
  • GET and HEAD requests and all responses were never affected.

Upgrading​

npm latest for mte-relay-browser-public-client is the v5 client, so pin the version when you install:

npm install mte-relay-browser-public-client@4.5.3
  • No code changes. mteFetch and its options are the same.
  • If you import the engine package mte-relay-browser directly, upgrade it to 4.4.3, which carries the same fix.
  • The trial web client mte-relay-browser-trial 4.4.3 carries the same fix. Install it from the new tarball URL on the Trial Build page.
  • Docs: Web JavaScript client and Version Compatibility.