Series: Axios Lesson 82

Failed Refresh Handling — Refresh muvaffaqiyatsiz bo'lganda logout va redirect

Refresh Token muddati tugaganda yoki bekor qilinganda toza chiqish (Graceful Logout) arxitekturasi: state tozalash, failedQueue rejection, redirect loop oldini olish va deep linking.

82-dars

Failed Refresh Handling — Refresh muvaffaqiyatsiz bo'lganda logout va redirect

Tasavvur qiling, foydalanuvchi tizimda bir haftadan beri bo'lmadi va uning uzoq muddatli Refresh Token seansi ham serverda butunlay tugadi (yoki administrator tomonidan xavfsizlik sababli bekor qilindi).

Foydalanuvchi ilovaga qaytib sahifani ochganda biror so'rov 401 Unauthorized xatosini oladi. Axios Response Interceptor fonda yashirincha POST /auth/refresh so'rovini yuboradi. Biroq server bu safar: "Sening Refresh Tokening ham yaroqsiz yoki muddati o'tgan" deb 401 yoki 403 Forbidden xatosini qaytaradi.

Bunday vaziyatda ilova shunchaki qotib qolmasligi, cheksiz yuklanishda (infinite spinner) turmasligi yoki konsolda nazoratsiz qizil xatolarni ko'rsatmasligi kerak. Tizim Graceful Logout (Toza va xavfsiz chiqish) amaliyotini bajarishi shart.


1. Graceful Logout nimalarni o'z ichiga oladi?

Tokenni yangilash muvaffaqiyatsiz chiqqanda (catch blokida) tizim quyidagi qat'iy tartibda tozalanishi lozim:

flowchart TD
    A["POST /auth/refresh muvaffaqiyatsiz (401/403)"] --> B["1. Xotirani tozalash\n(TokenManager.clearToken)"]
    B --> C["2. Web Storage tozalash\n(localStorage / sessionStorage)"]
    C --> D["3. Navbatdagi so'rovlarni rad etish\n(processQueue error bilan barcha Promiselarni yopadi)"]
    D --> E["4. Redirect Loop tekshiruvi\n(!window.location.pathname.includes('/login'))"]
    E --> F["5. Deep Linking bilan yo'naltirish\n(/login?redirect=...)"]
  1. Xotirani tozalash (Memory Cleanup): TokenManager ichidagi eskirgan access token darhol xotiradan o'chiriladi.
  2. Storage tozalash: Agar ilovada foydalanuvchi profili, roli yoki nozik sozlamalari localStorage yoki sessionStorageda saqlangan bo'lsa, ular to'liq o'chiriladi.
  3. Kutib turgan navbatni rad etish (failedQueue rejection): Yangi tokenni kutib Promise ichida osilib turgan barcha parallel so'rovlar xatolik bilan rad etiladi (reject qilinadi). Bu xotirada Promise memory leak yuzaga kelishining oldini oladi.
  4. Xavfsiz Redirect: Foydalanuvchi chiroyli tarzda Login sahifasiga yo'naltiriladi.

2. Amaliyot: Response Interceptor ichida Logout va Redirect

Keling, professional arxitekturada xatolik yuz berganda toza chiqishni ta'minlovchi handleLogoutAndRedirect funksiyasi va uning interceptor bilan integratsiyasini ko'rib chiqamiz:

// src/api/client.ts
import axios, { AxiosError, InternalAxiosRequestConfig } from 'axios';
import { TokenManager } from './tokenManager';

export const apiClient = axios.create({
  baseURL: 'https://api.mysite.com/v1',
  timeout: 10000,
  withCredentials: true,
});

let isRefreshing = false;

interface QueueItem {
  resolve: (token: string) => void;
  reject: (error: unknown) => void;
}

let failedQueue: QueueItem[] = [];

const processQueue = (error: unknown, token: string | null = null): void => {
  failedQueue.forEach((promise) => {
    if (error) {
      promise.reject(error);
    } else if (token) {
      promise.resolve(token);
    }
  });
  failedQueue = [];
};

// --- GLOBAL LOGOUT VA REDIRECT BOSHQARUVChISI ---
export const handleLogoutAndRedirect = (): void => {
  // 1. Xotiradagi tokenlarni tozalaymiz
  TokenManager.clearToken();

  // 2. Foydalanuvchi profili keshlarini tozalaymiz
  localStorage.removeItem('user_profile');
  localStorage.removeItem('auth_user');

  // 3. Cheksiz aylanish (Redirect Loop) oldini olamiz
  if (!window.location.pathname.includes('/login')) {
    // Foydalanuvchi turgan joriy sahifani query parametri sifatida saqlaymiz (Deep Linking)
    const currentPath = encodeURIComponent(window.location.pathname + window.location.search);
    window.location.href = `/login?redirect=${currentPath}`;
  }
};

// --- RESPONSE INTERCEPTOR ---
apiClient.interceptors.response.use(
  (response) => response,
  async (error: AxiosError) => {
    const originalRequest = error.config as (InternalAxiosRequestConfig & { _retry?: boolean }) | undefined;

    if (!originalRequest) {
      return Promise.reject(error);
    }

    if (error.response?.status === 401 && !originalRequest._retry) {
      
      // XAVFSIZLIK: Agar /auth/refresh so'rovining o'zi 401/403 qaytarsa -> DARHOL TOZA LOGOUT!
      if (originalRequest.url?.includes('/auth/refresh')) {
        handleLogoutAndRedirect();
        return Promise.reject(error);
      }

      // Agar boshqa bir so'rov allaqachon tokenni yangilashni boshlagan bo'lsa
      if (isRefreshing) {
        return new Promise<string>((resolve, reject) => {
          failedQueue.push({ resolve, reject });
        })
          .then((token) => {
            originalRequest.headers.Authorization = `Bearer ${token}`;
            return apiClient(originalRequest);
          })
          .catch((err) => Promise.reject(err));
      }

      originalRequest._retry = true;
      isRefreshing = true;

      try {
        // Yashirin refresh so'rovi
        const response = await axios.post<{ accessToken: string }>(
          'https://api.mysite.com/v1/auth/refresh',
          {},
          { withCredentials: true }
        );

        const newAccessToken = response.data.accessToken;
        TokenManager.setToken(newAccessToken);

        isRefreshing = false;
        processQueue(null, newAccessToken);

        originalRequest.headers.Authorization = `Bearer ${newAccessToken}`;
        return apiClient(originalRequest);

      } catch (refreshError) {
        // --- REFRESH MUVAFFAQIYATSIZ CHIQDI (Refresh Token ham yaroqsiz) ---
        isRefreshing = false;
        
        // 1. Kutib turgan barcha parallel so'rovlarni rad etamiz
        processQueue(refreshError, null);

        // 2. Seansni to'liq tozalab, foydalanuvchini login sahifasiga yo'naltiramiz
        handleLogoutAndRedirect();

        return Promise.reject(refreshError);
      }
    }

    return Promise.reject(error);
  }
);

3. Arxitektura bo'yicha muhim eslatmalar ⚠️

A. Redirect Loop (Cheksiz yo'naltirish) xavfining oldini olish

Tasavvur qiling: foydalanuvchi /login sahifasida turibdi. Ushbu sahifada qandaydir umumiy konfiguratsiya olish uchun API chaqirildi va server kutilmaganda 401 qaytardi.

Agar sizda !window.location.pathname.includes('/login') tekshiruvi bo'lmasa, interceptor foydalanuvchini yana /loginga yo'naltiradi, sahifa qayta ochilib yana o'sha API chaqiriladi va brauzer cheksiz miltillovchi qayta yuklanish (Redirect Loop) tuzog'iga tushib qoladi.

B. Deep Linking (Qaytish manzili)

Foydalanuvchi /dashboard/orders/125 sahifasida murakkab tahrirlash ishlarini olib borayotgan bo'lishi mumkin. Agar seans tugab u /loginga uloqtirilsa va qayta kirgandan so'ng asosiy sahifaga tushib qolsa, bu uning vaqtini o'g'irlaydi.

URL'ga ?redirect=${currentPath} parametrini biriktirish:

  1. Foydalanuvchi login formani to'ldirib tizimga kiradi;
  2. Tizim redirect parametrini o'qiydi va uni aynan o'zi to'xtagan sahifaga (/dashboard/orders/125) qaytaradi.

[!TIP] Hard Reload (window.location.href) ning afzalligi: SPA routerlari (react-routerdagi navigate('/login')) xotiradagi komponentlar va global state'ni (Zustand, Redux) to'liq tozalamasligi mumkin. window.location.href = '/login' qilish esa sahifani to'liq yangilaydi va xotiradagi barcha eski qoldiqlarni mutlaqo nollaydi.


4. Multi-tab Logout (Qo'shimcha tavsiya)

Agar foydalanuvchi brauzerda ilovaning bir nechta tablarini ochib qo'ygan bo'lsa va ulardan birida seans tugasa, boshqa tablar ham bundan xabardor bo'lishi kerak. Buni zamonaviy brauzerlarning BroadcastChannel yoki storage eventlari orqali amalga oshirish mumkin:

// Tablararo logout xabarini yuborish
const authChannel = new BroadcastChannel('auth_channel');

export const handleLogoutAndRedirect = (): void => {
  TokenManager.clearToken();
  localStorage.removeItem('user_profile');

  // Boshqa ochiq tablarga signal beramiz
  authChannel.postMessage({ type: 'LOGOUT' });

  if (!window.location.pathname.includes('/login')) {
    window.location.href = '/login';
  }
};

// Boshqa tablarda ushbu signalni eshitish:
authChannel.onmessage = (event) => {
  if (event.data?.type === 'LOGOUT') {
    TokenManager.clearToken();
    window.location.href = '/login';
  }
};

5. Oddiy Error Handling vs Graceful Logout

Mezon Oddiy Error Handling Graceful Logout
Refresh xato berganda Konsolda qizil xato, UI qotib qoladi Xotira va keshlar tozalanadi, toza chiqish bo'ladi
Parallel so'rovlar Javobsiz osilib qoladi (pending) failedQueue orqali toza rad etiladi (reject)
Foydalanuvchi tajribasi "Nima bo'ldi?" deb tushunmay qoladi Chiroyli tarzda login sahifasiga yo'naltiriladi
Qayta kirgandan so'ng Bosh sahifadan yana navigatsiya qilishga majbur Deep Linking orqali o'z sahifasiga qaytadi

Xulosa

Refresh Token mexanizmi faqatgina tokenni muvaffaqiyatli yangilash haqida emas, balki tokenni yangilash imkoni bo'lmaganda ilovani xavfsiz va madaniyatli boshqarish haqida hamdir. Graceful Logout, Deep Linking va Redirect Loop himoyasi har bir professional frontend dasturchining majburiy asboblar to'plamiga kirishi shart.