PPLX-55 - trckr

← PPLX-55

feature,web

Created: 2025-12-21 • Updated: 2025-12-21

Relationships Loading...

Add route protection and redirect unauthenticated users to login on 401 responses.

## Implementation
Update src/src/App.tsx:
1. Add route for /login
2. Add global 401 error interceptor
3. Redirect to /login?redirect=<current-path> on 401
4. After login, redirect to ?redirect param

## Approach
Add response interceptor or error boundary:
```typescript
// In fetch wrapper or error handler
if (response.status === 401) {
  const currentPath = window.location.pathname;
  window.location.href = `/login?redirect=${encodeURIComponent(currentPath)}`;
}
```

## Route Structure
```tsx
<Routes>
  <Route path="/login" element={<LoginPageContainer />} />
  
  {/* All other routes - protected by 401 redirect */}
  <Route path="/" element={<HomePageContainer />} />
  <Route path="/search/:threadId" element={<SearchResultsPageContainer />} />
  <Route path="/library" element={<LibraryPageContainer />} />
  {/* ... rest of routes */}
</Routes>
```

## Files to Modify
- src/src/App.tsx (add /login route)
- src/src/api/backend.ts (add 401 interceptor)

## Acceptance Criteria
- Login page accessible at /login
- Unauthenticated API requests (401) redirect to login
- Redirect param preserved in URL
- After login, user redirected to intended destination
- Browser refresh maintains auth (cookie persists)
- No infinite redirect loops
- Authenticated users accessing /login redirect to home

Pull Requests (comma-separated URLs)

Attachments

Comments (1)

agent · 2025-12-21

Implementation complete - merged to main. Login page accessible at /login with 401 redirect handling and redirect param preservation.