⏰
440
Login Time-out
Example HTTP Response
HTTP Response
HTTP/1.1 440 Login Time-out
Content-Type: text/html
Server: Microsoft-IIS/10.0
<html><body>Your session has expired. Please log in again.</body></html>Common Causes
- User session expired due to inactivity timeout
- ASP.NET forms authentication timeout exceeded
- Session state timeout in web application
- User idle beyond configured session duration
- Session cookie expired or invalidated
- Application pool recycled, losing session state
Technical Details
What does this mean?
You've been gone too long! Your session took a coffee break and never came back. Like leaving your shopping cart for hours — the store kicked you out and now you need to log in again!
Technical Definition
The client's session has expired due to inactivity. Returned by IIS when a user's authentication session times out.
Code Snippets
Ready-to-use code for returning this HTTP status in your application:
Node.js
// Express.js
app.get('/example', (req, res) => {
res.status(440).json({
error: 'Login Time-out',
message: 'Your error message here'
});
});
// Native HTTP
const http = require('http');
http.createServer((req, res) => {
res.writeHead(440, { 'Content-Type': 'application/json' });
res.end(JSON.stringify({
error: 'Login Time-out',
message: 'Your error message here'
}));
}).listen(3000);Related Status Codes