Summary
The POST /api/auth/refresh endpoint hangs instead of returning a response. The route exists in [authRoutes.js:] but the handler is empty, so refresh-token flows never complete.
Steps to reproduce
1.Start the backend server.
2.Send a post request to the [/api/auth/refresh].
3.Observe that the request times out and no response is returned.
Actual behavior
The request never completes. The server keeps the connection open because the route handler does not send any JSON response or error.
Expected behavior
The refresh endpoint should either:
return a new access token when refresh logic is implemented, or return a clear error response such as 501 Not Implemented or 400 Bad Request.
Reproduction details
- OS: [e.g. Windows 11, macOS 14]
- Browser / environment: Node.js backend API, PowerShell
- Version: [latest main branch from github
- Device: desktop
Additional context
The route is currently defined as:
authroute.js
Because the handler is empty, the client can hang waiting for a response.
Proposed fix (optional)
If you have an idea for the solution, share it here.
Implement refresh-token logic in the route handler, or return an explicit response until the feature is finished.
Summary
The POST /api/auth/refresh endpoint hangs instead of returning a response. The route exists in [authRoutes.js:] but the handler is empty, so refresh-token flows never complete.
Steps to reproduce
1.Start the backend server.
2.Send a post request to the [/api/auth/refresh].
3.Observe that the request times out and no response is returned.
Actual behavior
The request never completes. The server keeps the connection open because the route handler does not send any JSON response or error.
Expected behavior
The refresh endpoint should either:
return a new access token when refresh logic is implemented, or return a clear error response such as 501 Not Implemented or 400 Bad Request.
Reproduction details
Additional context
The route is currently defined as:
authroute.js
Because the handler is empty, the client can hang waiting for a response.
Proposed fix (optional)
If you have an idea for the solution, share it here.
Implement refresh-token logic in the route handler, or return an explicit response until the feature is finished.