Series: Axios Lesson 19

withCredentials — Cookie va credentials bilan ishlash

Axios'da withCredentials parametrining vazifasi: Cross-Origin so'rovlarda Cookie va sessiyalarni yuborish, HttpOnly refresh tokenlar va backend CORS talablari.

19-dars

withCredentials — Cookie va credentials bilan ishlash

Muammo nimada? (CORS va Cookie xavfsizligi)

Tasavvur qiling, sizning frontend ilovangiz http://localhost:5173 da ishlayapti, lekin backend serveringiz boshqa domenda — masalan, https://api.mysite.com.

Brauzerlarning CORS (Cross-Origin Resource Sharing) xavfsizlik qoidasiga ko'ra, agar so'rov boshqa domenga (cross-origin) ketayotgan bo'lsa, brauzer standart holatda cookie'larni (va boshqa shaxsiy ma'lumotlarni) so'rov bilan birga qo'shib yubormaydi. Natijada backend foydalanuvchi kimligini (tizimga kirganmi-yo'qmi) bilolmay qoladi.

withCredentials: true — bu Axios'ga (va brauzerga): "Iltimos, bu so'rov bilan birga cookie'larni va avtorizatsiya ma'lumotlarini ham qo'shib yubor" deb ko'rsatma beruvchi sozlamadir.

1. Axios instansiyasida withCredentials'ni yoqish

Agar sizning loyihangizda autentifikatsiya uchun cookie'lar (masalan, Refresh Token) ishlatilsa, bu sozlamani to'g'ridan-to'g'ri global axios.create() ichiga yozib qo'yish kerak:

import axios, { AxiosInstance } from 'axios';

export const apiClient: AxiosInstance = axios.create({
  baseURL: 'https://api.mysite.com/v1',
  timeout: 10000,
  // MUHIM: Barcha so'rovlar bilan birga Cookie'lar (masalan, refreshToken) yuborilishini ta'minlaydi
  withCredentials: true, 
  headers: {
    'Content-Type': 'application/json',
  },
});

2. Real misol: Cookie orqali avtorizatsiya (Login va Tokenni yangilash)

Keling, foydalanuvchi tizimga kirganda (login) va uning sessiyasi tugaganda cookie orqali token yangilangandagi (refresh) jarayonni ko'rib chiqamiz:

import { apiClient } from '../api/axios';

interface LoginCredentials {
  email: string;
  password: string;
}

interface UserProfile {
  id: number;
  email: string;
}

// 1. Tizimga kirish so'rovi
export const loginUser = async (credentials: LoginCredentials): Promise<UserProfile> => {
  // withCredentials: true tufayli, server javobidagi 'Set-Cookie' sarlavhasi 
  // brauzer tomonidan avtomatik ravishda saqlab qo'yiladi (HttpOnly cookie sifatida)
  const response = await apiClient.post<UserProfile>('/auth/login', credentials);
  return response.data;
};

// 2. Tokenni yangilash so'rovi (Refresh Token)
export const refreshToken = async (): Promise<void> => {
  // Bu yerda data yuborilmaydi, lekin withCredentials tufayli brauzer 
  // o'zidagi saqlangan cookie'ni serverga avtomatik jo'natadi
  await apiClient.post('/auth/refresh');
};

3. Backend (Server) tomonidan talab qilinadigan muhim shart

withCredentials: true ni faqat frontend'da yozib qo'yishning o'zi yetarli emas. Server tomoni ham bunga ruxsat berishi shart. Agar backend serveri CORS sozlamalarida quyidagi qoidalarni bajarmasa, brauzer so'rovni bloklab qo'yadi:

  1. Access-Control-Allow-Credentials: true header'i server tomonidan qaytarilishi shart.
  2. Access-Control-Allow-Origin sarlavhasida * (barcha domenlar) ishlatish taqiqlanadi — aniq domen ko'rsatilishi kerak (masalan: Access-Control-Allow-Origin: http://localhost:5173).