also fallback when you get 405 status code

Author: talge-a11y

src/modules/actors.ts

@@ -52,9 +52,11 @@ const DEAD_MS = 3_000;
 // Mint responses that mean "direct can't serve this connection, the proxy can":
 // 409 = legacy-family actor script, 503 = direct connections not provisioned,
 // 422 = no principal (e.g. anonymous outside a browser) or an id/room only the
-// proxy's looser validation accepts. The proxy serves migrated actors too, so
-// falling back is always safe.
-const PROXY_FALLBACK_STATUSES = new Set([409, 422, 503]);
+// proxy's looser validation accepts, 405 = a backend that predates the mint
+// endpoint (its actor deploy routes catch the path via `{handler_name:path}`
+// but not the POST method — and the real endpoint never 405s a POST). The
+// proxy serves migrated actors too, so falling back is always safe.
+const PROXY_FALLBACK_STATUSES = new Set([405, 409, 422, 503]);
 
 // Mint responses no retry can fix (bad request / forbidden / not found): the
 // connection closes instead of re-minting forever; a fresh connect() re-probes.

tests/unit/actors.test.ts

@@ -264,7 +264,7 @@ describe("Actors Module — proxy fallback", () => {
     );
   });
 
-  test.each([503, 422])("mint %i falls back to the proxy", async (status) => {
+  test.each([503, 422, 405])("mint %i falls back to the proxy", async (status) => {
     const config = makeConfig();
     config.mintConnectionToken.mockRejectedValueOnce(httpError(status));
     mod(config).GameRoom("r").connect({ id: "c" });
@@ -440,7 +440,7 @@ describe("Actors Module — mint error reporting", () => {
     expect(reported.message).toContain("boom");
   });
 
-  test.each([409, 422, 503])(
+  test.each([405, 409, 422, 503])(
     "the expected fallback status %i is silent",
     async (status) => {
       const config = makeConfig();
@@ -599,6 +599,27 @@ describe("Actors Module — client wiring", () => {
     base44.cleanup();
   });
 
+  test("a 405 mint reply (backend without the endpoint) falls back to the proxy", async () => {
+    // What a pre-direct backend actually answers: its actor deploy routes
+    // match the path via `{handler_name:path}` but not the POST method.
+    nock(serverUrl)
+      .post(`/api/apps/${appId}/actors/PongGame/connection-token`)
+      .reply(405, {
+        error_type: "HTTPException",
+        message: "Method Not Allowed",
+        detail: "Method Not Allowed",
+      });
+
+    const onError = vi.fn();
+    const base44 = createClient({ serverUrl, appId, token: "tok", options: { onError } });
+    base44.actors.PongGame("r1").connect({ id: "c1" });
+    await expect(sockets[0].urlProvider()).resolves.toBe(
+      "wss://base44.app/parties/PongGame/r1?_pk=c1&app_id=app-1&handler=PongGame&token=tok",
+    );
+    expect(onError).not.toHaveBeenCalled();
+    base44.cleanup();
+  });
+
   test("a non-fallback mint failure reaches the client's onError as a Base44Error", async () => {
     nock(serverUrl)
       .post(`/api/apps/${appId}/actors/PongGame/connection-token`)