Infinite Refresh Loop Prevention — Cheksiz refresh siklining oldini olish
Axios interceptorlarida cheksiz refresh siklining (Infinite Loop) oldini olish: URL istisnolari, _retry bayrog'i, retry counter chegaralari va fail-safe forceLogout arxitekturasi.
84-dars
Infinite Refresh Loop Prevention — Cheksiz refresh siklining oldini olish
Tasavvur qiling, qandaydir nosozlik tufayli server yangi Access Token bergandan keyin ham so'rovlarga doimiy ravishda 401 Unauthorized xatosini qaytarmoqda (masalan, backend konfiguratsiyasida xatolik bor yoki Refresh Tokenning o'zi ham allaqachon bekor qilingan).
Agar Response Interceptor'da maxsus himoya to'siqlari o'rnatilmagan bo'lsa, quyidagi halokatli sikl (Infinite Refresh Loop) yuzaga keladi:
flowchart TD
A["So'rov ketdi (GET /profile)"] --> B["Server 401 Unauthorized qaytardi"]
B --> C["Interceptor /auth/refresh ga so'rov yubordi"]
C --> D["Server /auth/refresh ga ham 401 qaytardi!"]
D --> E["Interceptor buni oddiy 401 deb tushundi"]
E --> C
style C fill:#ff4d4f,stroke:#fff,color:#fff
style D fill:#ff4d4f,stroke:#fff,color:#fff
style E fill:#ff4d4f,stroke:#fff,color:#fff
Bu jarayon soniyasiga yuzlab marta takrorlanib:
- Brauzer xotirasi va protsessorini to'ldirib, sahifani to'liq qotirib qo'yadi (browser freeze);
- Serverga o'z-o'zidan DDoS (Distributed Denial of Service) hujumini hosil qilib, API shlyuzini ishdan chiqaradi;
- Tarmoq limitlarini (rate limits) lahzalar ichida tugatadi.
1. Cheksiz siklning 3 ta asosiy sababi
- Refresh endpointning o'zi
401qaytarganda: Refresh Token eskirgan bo'lsa, server/auth/refreshchaqiruviga ham 401 beradi. Interceptor buni odatiy so'rov deb o'ylab, yana refresh chaqirsa, cheksiz halqa hosil bo'ladi. - Replay qilingan so'rov yana
401olganda: Yangi token olinib, asl so'rov takrorlanganda (replay), agar u yana 401 olsa va cheklov bo'lmasa, jarayon boshidan boshlanadi. - Rekursiv Interceptor tuzog'i: Agar refresh so'rovi xuddi shu interceptor ulangan
apiClientorqali yuborilsa, refresh so'rovining xatosi yana o'sha interceptorga tushadi.
2. Uch bosqichli himoya qalqoni (3-Tier Defense Mechanism)
Professional frontend arxitekturada cheksiz sikllarni yo'q qilish uchun 3 ta qat'iy himoya qoidasi joriy etiladi:
flowchart TD
A["401 Unauthorized Xatosi Keldi"] --> B{"1. originalRequest.url\n/auth/refresh ga tegishlimi?"}
B -->|Ha (Refresh o'lgan)| Z["forceLogout() & So'rovni to'xtatish"]
B -->|Yo'q| C{"2. originalRequest._retry\nallaqachon true mi?"}
C -->|Ha (Takroriy 401)| Z
C -->|Yo'q| D["originalRequest._retry = true qo'yish"]
D --> E["Yashirin POST /auth/refresh"]
E -->|Muvaffaqiyatli| F["Yangi token bilan so'rovni takrorlash (Replay)"]
E -->|Xatolik (catch)| Z
- URL Exclusion (Refresh endpointini chetlab o'tish):
Agar xatolik bergan so'rovning o'zi
/auth/refreshmanziliga tegishli bo'lsa, hech qanday yangilashga urinmasdan, darhol to'xtatish va toza logout qilish. _retryBayrog'i (Bir martalik cheklov): Har bir so'rovga maxsus_retry = truebelgisi qo'yiladi. So'rov faqat bir marta qayta urinish (retry) huquqiga ega. Agar qayta yuborilgan so'rov yana 401 olsa, uni qayta takrorlash qat'iyan man etiladi.- Fail-Safe ForceLogout (Xavfsiz chiqish):
Har qanday kutilmagan holat yoki token yangilash muvaffaqiyatsizligida xotirani darhol tozalash va foydalanuvchini
/loginsahifasiga yo'naltirish.
3. Amaliyot: TypeScript va Axios Response Interceptor'da Himoya
Keling, barcha ushbu xavfsizlik choralari birlashtirilgan to'liq kodni 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,
});
// Axios config kengaytmasi
interface CustomRequestConfig extends InternalAxiosRequestConfig {
_retry?: boolean;
}
let isRefreshing = false;
interface QueueItem {
config: CustomRequestConfig;
resolve: (value: any) => void;
reject: (error: unknown) => void;
}
let failedQueue: QueueItem[] = [];
const processQueue = (error: unknown, token: string | null = null): void => {
failedQueue.forEach((item) => {
if (error) {
item.reject(error);
} else if (token) {
if (item.config.headers) {
item.config.headers.Authorization = `Bearer ${token}`;
}
item.resolve(apiClient(item.config));
}
});
failedQueue = [];
};
/**
* Cheksiz sikllardan qutqaruvchi xavfsiz logout funksiyasi
*/
const forceLogout = (): void => {
TokenManager.clearToken();
localStorage.removeItem('user_profile');
// Agar allaqachon login sahifasida bo'lmasa, yo'naltiramiz
if (!window.location.pathname.includes('/login')) {
const returnUrl = encodeURIComponent(window.location.pathname + window.location.search);
window.location.href = `/login?redirect=${returnUrl}`;
}
};
apiClient.interceptors.response.use(
(response) => response,
async (error: AxiosError) => {
const originalRequest = error.config as CustomRequestConfig | undefined;
if (error.response?.status === 401 && originalRequest) {
// --- 1-HIMOYA: REFRESH ENDPOINT'NING O'ZIDAN 401 KELSA ---
// Agar so'rovning manzili /auth/refresh bo'lsa, demak Refresh Token ham yaroqsiz!
if (originalRequest.url?.includes('/auth/refresh')) {
forceLogout();
return Promise.reject(error);
}
// --- 2-HIMOYA: _retry BAYROG'I ORQALI BIR MARTALIK CHEKLOV ---
// Agar bu so'rov allaqachon bir marta takrorlangan bo'lsa va yana 401 olsa:
if (originalRequest._retry) {
forceLogout();
return Promise.reject(error);
}
// Bir martalik urinish bayrog'ini yoqamiz
originalRequest._retry = true;
// Agar boshqa bir so'rov ayni paytda tokenni yangilayotgan bo'lsa, navbatga qo'shamiz
if (isRefreshing) {
return new Promise((resolve, reject) => {
failedQueue.push({ config: originalRequest, resolve, reject });
});
}
isRefreshing = true;
try {
// --- 3-HIMOYA: MUSTAQIL AXIOS INSTANSIYASI ---
// Rekursiv interceptor tuzog'iga tushmaslik uchun toza axios chaqiriladi
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);
// Birinchi so'rovni yangi token bilan qayta yuboramiz
if (originalRequest.headers) {
originalRequest.headers.Authorization = `Bearer ${newAccessToken}`;
}
return apiClient(originalRequest);
} catch (refreshError) {
// Refresh jarayonining o'zi xatoga uchrasa (masalan, tarmoq uzilsa yoki 403 kelsa)
isRefreshing = false;
processQueue(refreshError, null);
forceLogout();
return Promise.reject(refreshError);
}
}
return Promise.reject(error);
}
);
4. Muhim xavfsizlik qoidalari ⚠️
[!CAUTION] 401 vs 403 Farqini unutmang:
401 Unauthorized— Foydalanuvchining autentifikatsiyasi (ruxsatnomasi) eskirgan yoki yo'q. Faqat shu holatdagina token yangilanadi.403 Forbidden— Foydalanuvchi tizimga kirgan, lekin uning huquqi (Role/Permission) bu amalni bajarishga yetarli emas. 403 xatolarida hech qachon refresh so'rovi yuborilmasligi kerak!
[!TIP] Hech qachon shartsiz qayta takrorlamang (Never Retry Blindly): Har qanday asinxron retry yoki refresh mantiqida qat'iy to'xtatish sharti bo'lishi shart. Agar tizim bitta operatsiyani 1 martadan ortiq takrorlayotgan bo'lsa, qat'iy maksimal limit (masalan,
maxRetries: 1) qo'yilishi shart.
5. Himoyalanmagan vs Himoyalangan Interceptor
| Xususiyat | Himoyalanmagan Interceptor | Himoyalangan Interceptor (3-Tier) |
|---|---|---|
| Refresh endpoint 401 bersa | Cheksiz sikl hosil bo'ladi | Darhol to'xtatilib, forceLogout() bajariladi |
| Replay qilingan so'rov yana 401 bersa | Qayta-qayta yangilashga urinadi | _retry flagi tufayli to'xtatiladi |
| Brauzer holati | Xotira to'lib, sahifa qotadi (Freeze) | Xavfsiz login sahifasiga yo'naltiriladi |
| Serverga ta'siri | Sun'iy DDoS va ortiqcha so'rovlar | Minimal va qat'iy bitta so'rov |
Xulosa
Cheksiz refresh sikli — frontend dasturchilar bilmasdan yo'l qo'yadigan eng xavfli xatolardan biridir. URL Exclusion, _retry flagi va Fail-safe ForceLogout qoidalariga qat'iy rioya qilish orqali siz ilovangizni nafaqat barqaror, balki har qanday kutilmagan server xatoliklariga bardoshli qilib qurasiz.