Package.json file
{
"dependencies": {
"@medusajs/framework": "2.21.1",
"@medusajs/medusa": "2.21.1"
}
}
Node.js version
v22.23.3
Database and its version
PostgreSQL 17
Operating system name and version
Arch Linux (kernel 7.2), also a Docker image on Unraid
Browser name
Not browser specific
What happended?
With the index engine flag off (the default), a signed-in admin's request to GET /admin/index/details or POST /admin/index/sync never receives a response. isIndexEnabledMiddleware in packages/medusa/src/api/admin/index/middlewares.ts logs "Trying to access '/admin/index/*' route but the index module is not configured" and then does return res.status(404), which sets the status without sending anything, so the request stays open until the client gives up. The same code is on develop today.
Expected behavior
The middleware answers 404 and ends the response, for example res.status(404).json({ type: "not_found", message: "..." }).
Actual behavior
The connection stays open with no response; a client with a 15 second timeout gave up after 15 seconds, on 2.21.1.
Link to reproduction repo
No separate repository: any 2.21.1 project with the index engine flag left off shows it. Sign in as an admin and request with a client timeout.