I’m migrating a deployment over from Lambda + API Gateway to Fly. I’ve got it all deployed to Fly just fine, but super weird - our sign-in page works from Chrome, but not Safari. Same code for that route works fine on the Lambda deployment on both Safari and Chrome, and it works fine locally, too. Safari’s console shows:
Failed to load resource: cannot parse response. The request shows
- for the status of the response, no response headers, nothing. It’s like the request just died. However, the logs in Fly show a 204 being returned.
Again - I can run the exact same code locally, and it works in both Safari and Chrome as expected, and a very similar variant (only differing in package shape to get it running on Lambda) also works as expected there.
As noted in the title, this is a Remix app. Anyone have any idea why this one specific case is acting up?