Enduriel Posts - Answer Overflow

Enduriel

•Created by Enduriel on 3/24/2024 in #workers-help

Worker Erroring attempting HTTP 100 in Remote Mode with Content-Length > 1024 on older client

Seems to be a very strange set of circumstances required to reproduce this issue, but I have been able to narrow down when it doesn't happen at least. The TLDR is that the worker fails to run if the POST request I make with my client has a content length > 1024. This only happens when - using wrangler dev --remote (both deploy and local work fine) - Request Content-Length > 1024, this seems to trigger an HTTP 100 Response somehow - I use an older custom chromium client (specifically the chromium build based on version ~45 used by the game Battle Brothers), I was unable to reproduce this on both postman and a clean chromium v45 build Symptoms When using a fresh JS worker hello world build, I get the error:

Error in ProxyController: Error inside ProxyWorker

   {
    name: 'RangeError',
    message: 'Responses may only be constructed with status codes in the range 200 to 599,
  inclusive.',
    stack: 'RangeError: Responses may only be constructed with status codes in the range 200 to 599,
  inclusive.\n' +
      '    at
  file:///C:/Users/End/AppData/Local/Volta/tools/image/packages/wrangler/node_modules/wrangler/wrangler-dist/ProxyWorker.js:113:15'
  }

Error in ProxyController: Error inside ProxyWorker

   {
    name: 'RangeError',
    message: 'Responses may only be constructed with status codes in the range 200 to 599,
  inclusive.',
    stack: 'RangeError: Responses may only be constructed with status codes in the range 200 to 599,
  inclusive.\n' +
      '    at
  file:///C:/Users/End/AppData/Local/Volta/tools/image/packages/wrangler/node_modules/wrangler/wrangler-dist/ProxyWorker.js:113:15'
  }

By hacking my way into the source there, I was able find out what the response it's try to send actually is and it's an HTTP 100/Continue response. This seems like a really annoying edge case scenario, but it doesn't seem to be the 'fault' of the client, since local development, full deployment and other APIs work completely fine. I'm happy to help with trying to figure this out as it makes development more difficult, and might come up in other situations. I am by no means an expert in workers, http or any of the other stuff involved here, so let me know if i'm doing anything stupid

1 replies

Gaming

Programming