SSR Compatibility — Server-side rendering muhitida Axios ishlatish
Next.js, Remix va Node.js SSR muhitlarida Axios bilan ishlash: typeof window !== 'undefined' tekshiruvlari, Request Isolation (foydalanuvchi ma'lumotlari aralashib ketishining oldini olish), cookie/header forwarding va universal factory pattern.
108-dars
SSR Compatibility — Server-side rendering muhitida Axios ishlatish
Zamonaviy frontend arxitekturalarida (Next.js, Remix, Nuxt yoki Node.js Express asosidagi SSR tizimlari) ilova kodi faqat brauzerda emas, balki ikki xil muhitda navbatma-navbat ishlaydi:
- Server tomonida (Node.js / Edge Runtime): Dastlabki HTML sahifani tezkor yaratish paytida;
- Mijoz tomonida (Brauzer / Client-side Hydration): Foydalanuvchi interfeys bilan muloqot qilayotgan paytda.
Bunday gibrid muhitda odatiy Axios sozlamalarini to'g'ridan-to'g'ri ishlatish kutilmagan xatoliklarga va jiddiy kiberxavfsizlik zaifliklariga olib kelishi mumkin.
1. SSR Muhitining 3 Ta Kritik Muammosi ⚠️
flowchart TD
subgraph BrowserEnv["1. Brauzer Muhiti (Client-side)"]
B1["window mavjud"]
B2["localStorage mavjud"]
B3["1 ta foydalanuvchi sessiyasi"]
end
subgraph ServerEnv["2. Server Muhiti (Node.js SSR)"]
S1["❌ window yo'q (ReferenceError)"]
S2["❌ localStorage yo'q"]
S3["⚠️ Yuzlab parallel foydalanuvchilar (Request Isolation xavfi)"]
end
1. window va localStorage ning mavjud emasligi
Server (Node.js) muhitida brauzerning global window, document yoki localStorage obyektlari mavjud emas. Agar sizning Axios interceptoringizda to'g'ridan-to'g'ri localStorage.getItem('token') yozilgan bo'lsa, server sahifani chizish vaqtida darhol halokatli xato bilan qulaydi:
ReferenceError: localStorage is not defined
2. So'rovlar Izolyatsiyasi (Request Isolation — Eng xavfli xato!)
Brauzerda yagona apiClient instansiyasi va xotiradagi token faqat bitta kompyuter egasiga tegishli bo'ladi.
Biroq SSR serverida bitta Node.js jarayoni bir vaqtning o'zida yuzlab turli foydalanuvchilarning so'rovlariga javob beradi. Agar siz tokenni faylning yuqori qismidagi global o'zgaruvchida saqlasangiz:
[!CAUTION] Data Leakage (Ma'lumotlar sizishi): A foydalanuvchining shaxsiy tokeni B foydalanuvchining so'roviga birikib ketishi va B foydalanuvchi A ning profil ma'lumotlarini ko'rib qolishi mumkin!
3. Cookie va Sarlavhalarni Uzatish (Cookie Forwarding)
Brauzerda withCredentials: true cookielarni avtomatik yuboradi. Ammo SSR paytida so'rov serverdan serverga (SSR Server ➔ Backend API) ketadi. Shuning uchun foydalanuvchi brauzeridan SSR serveriga kelgan Cookie sarlavhasini Axios orqali Backend API'ga qo'lda uzatib yuborish (forwarding) shart.
2. Yechim: Universal Factory Pattern (createSsrApiClient)
Har bir kiruvchi so'rov uchun xavfsiz va izolyatsiyalangan yangi Axios instansiyasini yaratuvchi Factory funksiya tuzamiz:
// src/shared/api/ssrClient.ts
import axios, { AxiosInstance, InternalAxiosRequestConfig } from 'axios';
// Kod serverda yoki brauzerda ishlayotganini aniqlaymiz
export const isServer = typeof window === 'undefined';
/**
* SSR va Brauzer uchun universal Axios mijozini yaratuvchi fabrika
* @param reqHeaders Serverda bo'lganda foydalanuvchi brauzeridan kelgan sarlavhalar (Cookies/Auth)
*/
export const createSsrApiClient = (
reqHeaders?: Record<string, string | string[] | undefined>
): AxiosInstance => {
const instance = axios.create({
baseURL: process.env.VITE_API_BASE_URL || 'https://api.mysite.com/v1',
timeout: isServer ? 5000 : 15000, // Serverda sahifa tez yuklanishi uchun qisqa timeout
headers: {
'Content-Type': 'application/json',
// Agar serverda bo'lsak, brauzerdan kelgan cookielarni API ga o'tkazamiz
...(isServer && reqHeaders?.cookie ? { Cookie: String(reqHeaders.cookie) } : {}),
...(isServer && reqHeaders?.authorization ? { Authorization: String(reqHeaders.authorization) } : {}),
},
withCredentials: true,
});
// Request Interceptor: Faqat brauzerda localStorage'dan tokenni o'qiydi
instance.interceptors.request.use(
(config: InternalAxiosRequestConfig) => {
// ⚠️ SERVERDA LOCALSTORAGE CHAQRILMAYDI!
if (!isServer) {
const token = localStorage.getItem('access_token');
if (token && config.headers) {
config.headers.Authorization = `Bearer ${token}`;
}
}
return config;
},
(error) => Promise.reject(error)
);
return instance;
};
// Brauzer muhiti uchun bitta qayta ishlatiladigan umumiy instansiya (Singleton)
export const browserApiClient = !isServer ? createSsrApiClient() : null;
3. Server Tomonida Ma'lumotlarni Yuklash (Next.js / SSR Namunasi)
SSR freymvorkida (masalan, Next.js getServerSideProps yoki Remix loader funksiyasida) ushbu fabrikadan foydalanish:
// pages/dashboard.tsx (Next.js Pages Router namunasi)
import { GetServerSideProps } from 'next';
import { createSsrApiClient } from '../src/shared/api/ssrClient';
interface DashboardProps {
userProfile: { id: string; name: string } | null;
ordersCount: number;
}
export const getServerSideProps: GetServerSideProps<DashboardProps> = async (context) => {
// 1. Foydalanuvchi brauzeridan kelgan sarlavhalarni (shu jumladan sessiya cookielarini) uzatamiz
const ssrApi = createSsrApiClient(context.req.headers);
try {
// 2. Server nomidan Backend API ga xavfsiz so'rov yuboramiz
const [profileRes, ordersRes] = await Promise.all([
ssrApi.get('/users/me'),
ssrApi.get('/orders/count'),
]);
return {
props: {
userProfile: profileRes.data,
ordersCount: ordersRes.data.count,
},
};
} catch (error) {
// Sessiya yaroqsiz bo'lsa, server darajasida darhol login sahifasiga yo'naltiramiz
return {
redirect: {
destination: '/login',
permanent: false,
},
};
}
};
sequenceDiagram
autonumber
actor User as Foydalanuvchi Brauzeri
participant SSR as Next.js SSR Server
participant Backend as Backend API Server
User->>SSR: 1. Sahifani so'rash (Cookie: session_id=123)
Note over SSR: createSsrApiClient(req.headers) yaratiladi
SSR->>Backend: 2. GET /users/me (Cookie: session_id=123 forward qilinadi)
Backend-->>SSR: 3. 200 OK (Foydalanuvchi ma'lumotlari)
Note over SSR: HTML sahifa to'liq generatsiya qilinadi
SSR-->>User: 4. Tayyor HTML qaytariladi (Darhol ko'rinadi)
4. SSR Uchun 4 Ta Oltin Qoida 🚀
typeof window !== 'undefined'tekshiruvi: Brauzerga xos barcha API'larga (localStorage,sessionStorage,navigator,document) murojaat qilishdan oldin ushbu tekshiruvni o'tkazish shart.- Serverda Global Token Saqlamang: Har bir kiruvchi SSR so'rovi uchun
createSsrApiClient(req.headers)orqali alohida izolyatsiyalangan mijoz yarating. - Server Timeout'ini Qisqaroq Qiling: Brauzerda so'rov 15 soniya kutishi mumkin, ammo SSR serverida 15 soniya kutish butun sahifa yuklanishini to'xtatib qo'yadi. SSR uchun 3–5 soniyalik timeout eng maqbuli.
- Ichki Tarmoq (Private Network) Imkoniyati: SSR serveri va Backend ko'pincha bitta data-markazda bo'ladi. Serverda ommaviy internet orqali emas, ichki tezkor IP (
http://internal-api:8080) orqali so'rov yuborish sahifani bir necha barobar tezlashtiradi.
5. Client-Only vs SSR-Compatible Axios
| Mezon | Standart Client-Only Axios | SSR-Compatible Axios |
|---|---|---|
window tekshiruvi |
Yo'q (localStorage to'g'ridan-to'g'ri o'qiladi) |
typeof window !== 'undefined' orqali himoyalangan |
| Instansiya turi | Global Singleton | Brauzerda Singleton, Serverda Factory |
| Foydalanuvchilar xavfsizligi | Faqat 1 ta brauzer egasi | Har bir so'rov qat'iy izolyatsiyalangan |
| Cookie yetkazish | Brauzer avtomatik qo'shadi | Serverdan backendga qo'lda forward qilinadi |
| Timeout qiymati | Odatda 10s – 15s | Serverda 3s – 5s, brauzerda 10s – 15s |
Xulosa
SSR (Server-Side Rendering) muhitida Axios bilan ishlashda eng muhim qoida — bu muhitlarni to'g'ri ajratish va Request Isolation tamoyiliga qat'iy rioya qilishdir. Universal Factory Pattern orqali yaratilgan createSsrApiClient serverda ham, brauzerda ham xatolarsiz, xavfsiz va yuqori tezlikda ma'lumot almashishni kafolatlaydi.