Shared API Client — Loyihada yagona va qayta ishlatiladigan API client
Loyihada yagona va qayta ishlatiladigan Shared API Client arxitekturasi: Single Source of Truth, Request/Response interceptorlar, xavfsiz token boshqaruvi, timeout va CORS sozlamalari.
105-dars
Shared API Client — Loyihada yagona va qayta ishlatiladigan API client
Yirik frontend ilovalarida barcha tarmoq so'rovlari uchun yagona, markazlashgan va to'g'ri sozlangan Shared API Client bo'lishi shart.
Har bir komponent yoki servis ichida har xil usulda axios.create() chaqirish yoki global axios obyektini nazoratsiz ishlatish quyidagi jiddiy muammolarga olib keladi:
- Interceptorlarning tarqoqligi: 401 xatosi kelganda tokenni yangilash faqat ayrim so'rovlarda ishlab, boshqalarida ishlamay qoladi.
- Turli xil timeout va URL'lar: Har xil qismlarda har xil vaqt chegaralari va xatoliklar kelib chiqadi.
- Xavfsizlik zaifliklari: Sarlavhalar va cookie sozlamalari to'liq nazorat qilinmaydi.
Shu sababli butun loyiha uchun yagona haqiqat manbasi (Single Source of Truth) hisoblangan umumiy API mijozini yaratamiz.
1. Shared API Client'ning 4 Ta Asosiy Vazifasi
flowchart TD
subgraph Services["Loyihadagi Barcha Servislar"]
S1["AuthService"]
S2["UserService"]
S3["TodoService"]
end
subgraph SharedClient["src/shared/api/client.ts (Yagona Darvoza)"]
ReqInt["1. Request Interceptor\n(Bearer Token biriktirish)"]
Config["2. Asosiy Sozlamalar\n(baseURL, timeout: 15s, withCredentials)"]
ResInt["3. Response Interceptor\n(401 Silent Refresh & Logout)"]
end
Services --> ReqInt
ReqInt --> Config
Config --> Network["Backend API"]
Network --> ResInt
ResInt --> Services
- Markazlashtirilgan Konfiguratsiya: Bazaviy URL (
baseURL), vaqt chegarasi (timeout), umumiy sarlavhalar (headers) va cookie almashinuvi (withCredentials: true). - Autentifikatsiya Oqimi: Har bir chiquvchi so'rovga mavjud tokenni avtomatik biriktirish.
- Silent Refresh & Error Recovery:
401 Unauthorizedxatosi kelganda foydalanuvchiga sezdirmasdan tokenni yangilash va so'rovni qayta yuborish (replay). - Xavfsiz Chiqish (Graceful Logout): Sessiya muddati to'liq tugaganda xotirani tozalab, foydalanuvchini xavfsiz login sahifasiga yo'naltirish.
2. Amaliyot: Production-Ready src/shared/api/client.ts
Quyida barcha talablarni to'liq o'z ichiga olgan, TypeScript va Axios yordamida yozilgan professional umumiy mijoz keltirilgan:
// src/shared/api/client.ts
import axios, {
AxiosInstance,
AxiosError,
InternalAxiosRequestConfig,
AxiosResponse,
} from 'axios';
// 1. Qayta urinish bayrog'i (_retry) uchun konfiguratsiya interfeysi
export interface CustomRequestConfig extends InternalAxiosRequestConfig {
_retry?: boolean;
skipAuth?: boolean;
}
// 2. Global Axios instansiyasini yaratamiz (Singleton)
export const apiClient: AxiosInstance = axios.create({
// Muhit o'zgaruvchisidan o'qiymiz yoki standart URL'ni qo'yamiz
baseURL: import.meta.env.VITE_API_BASE_URL || 'https://api.mysite.com/v1',
timeout: 15000, // 15 soniya timeout
headers: {
'Content-Type': 'application/json',
Accept: 'application/json',
},
withCredentials: true, // HttpOnly Cookie (Refresh token) almashinuvi uchun shart
});
// 3. REQUEST INTERCEPTOR: Tokenni har bir so'rovga avtomatik qo'shish
apiClient.interceptors.request.use(
(config: InternalAxiosRequestConfig) => {
const customConfig = config as CustomRequestConfig;
// Agar ommaviy so'rov bo'lsa (login, register), tokenni qo'shmaymiz
if (customConfig.skipAuth) {
return config;
}
// Tokenni xotiradan yoki saqlagichdan olamiz
const token = localStorage.getItem('access_token');
if (token && config.headers) {
config.headers.Authorization = `Bearer ${token}`;
}
return config;
},
(error: AxiosError) => {
return Promise.reject(error);
}
);
// 4. RESPONSE INTERCEPTOR: Xatoliklar va 401 Silent Refresh logikasi
apiClient.interceptors.response.use(
(response: AxiosResponse) => response,
async (error: AxiosError) => {
const originalRequest = error.config as CustomRequestConfig | undefined;
// 401 (Unauthorized) bo'lsa va bu so'rov hali qayta takrorlanmagan bo'lsa:
if (error.response?.status === 401 && originalRequest && !originalRequest._retry) {
// Cheksiz siklning oldini olamiz (agar /auth/refresh so'rovining o'zi 401 bersa)
if (originalRequest.url?.includes('/auth/refresh')) {
localStorage.removeItem('access_token');
window.location.href = '/login';
return Promise.reject(error);
}
originalRequest._retry = true;
try {
// Yashirin refresh so'rovini toza axios orqali yuboramiz
const refreshUrl = `${apiClient.defaults.baseURL}/auth/refresh`;
const res = await axios.post<{ accessToken: string }>(
refreshUrl,
{},
{ withCredentials: true }
);
const newAccessToken = res.data.accessToken;
localStorage.setItem('access_token', newAccessToken);
// Asl so'rov sarlavhasini yangilaymiz
if (originalRequest.headers) {
originalRequest.headers.Authorization = `Bearer ${newAccessToken}`;
}
// To'xtab qolgan so'rovni yangi token bilan takrorlaymiz (Replay)
return apiClient(originalRequest);
} catch (refreshError) {
// Refresh token ham eskirgan bo'lsa -> toza logout
localStorage.removeItem('access_token');
if (!window.location.pathname.includes('/login')) {
const returnUrl = encodeURIComponent(window.location.pathname + window.location.search);
window.location.href = `/login?redirect=${returnUrl}`;
}
return Promise.reject(refreshError);
}
}
return Promise.reject(error);
}
);
3. Muhim Nozik Jihatlar va Ehtiyot Choralari ⚠️
A. Rekursiyadan Saqlanish (Infinite Loop Prevention)
Diqqat qiling: Refresh so'rovi yuborilayotganda apiClient.post() emas, balki toza axios.post() chaqiriladi.
[!NOTE] Agar
apiClient.post('/auth/refresh')qilinsa, uning o'zi ham xuddi shu interceptor zanjiriga tushadi va agar u 401 bersa, cheksiz sikl boshlanib ketishi mumkin. Mustaqilaxioschaqiruvi bu xavfni to'liq bartaraf etadi.
B. timeout: 15000 (15 Soniya Cheklovi)
So'rovlarga hech qanday timeout o'rnatilmasligi — ilovaning eng xavfli kamchiligidir. Agar server javob bermay qotsa, foydalanuvchi ekranda cheksiz aylanuvchi spinner ko'rib o'tirishga majbur bo'ladi. 15 soniyalik chegara tarmoq uzilishlarida tezkor xatolik qaytarishni ta'minlaydi.
C. withCredentials: true
Refresh Token ko'pincha HttpOnly Cookie formatida keladi. Ushbu parametr bo'lmasa, brauzer so'rovga cookie'larni qo'shib yubormaydi va token yangilash imkonsiz bo'lib qoladi.
4. Tarqoq Instansiyalar vs Yagona Shared Client
| Xususiyat | ❌ Tarqoq Instansiyalar | ✅ Yagona Shared Client |
|---|---|---|
| Konfiguratsiya | Har bir faylda qo'lda takrorlanadi | Faqat src/shared/api/client.ts da yoziladi |
| Token boshqaruvi | Ba'zi servislarda unutiladi | Barcha so'rovlarga avtomatik qo'shiladi |
| 401 Silent Refresh | Alohida-alohida qayta yozishga majbur | Barcha so'rovlar uchun markazlashgan |
| O'zgartirish kiritish | 50 ta faylni tahrirlash talab etiladi | Faqat 1 ta fayl o'zgartiriladi |
| Xavfsizlik | Zaifliklar ko'p | Qat'iy nazorat ostida |
Xulosa
Shared API Client — har qanday jiddiy va professional veb-ilovaning eng mustahkam poydevoridir. Barcha tarmoq amaliyotlarini yagona nuqtaga (Single Source of Truth) bog'lash orqali biz nafaqat kodni toza va tartibli saqlaymiz, balki xavfsizlik va avtomatik token yangilanishini butun ilova bo'ylab 100% kafolatlaymiz.