| Server IP : 217.160.0.135 / Your IP : 216.73.217.85 Web Server : Apache System : Linux www 6.18.52-i1-ampere #1203 SMP Mon Sep 14 18:29:59 CEST 2026 aarch64 User : sws1074145052 ( 1074145052) PHP Version : 8.3.32 Disable Function : NONE MySQL : OFF | cURL : ON | WGET : ON | Perl : ON | Python : OFF | Sudo : OFF | Pkexec : OFF Directory : /lib/python3/dist-packages/django/core/checks/security/__pycache__/ |
Upload File : |
�
�|�e� � �
� d dl Z d dlmZ ddlmZmZmZmZ edd�� � Z edd �� � Z d
� Z
eej d�� � d
� � � Z eej d�� � d� � � Z
eej � � d� � � ZdS )� N)�settings� )�Error�Tags�Warning�registera You don't appear to be using Django's built-in cross-site request forgery protection via the middleware ('django.middleware.csrf.CsrfViewMiddleware' is not in your MIDDLEWARE). Enabling the middleware is the safest approach to ensure you don't leave any holes.z
security.W003��idz�You have 'django.middleware.csrf.CsrfViewMiddleware' in your MIDDLEWARE, but you have not set CSRF_COOKIE_SECURE to True. Using a secure-only CSRF cookie makes it more difficult for network traffic sniffers to steal the CSRF token.z
security.W016c � � dt j v S )Nz)django.middleware.csrf.CsrfViewMiddleware)r �
MIDDLEWARE� � �B/usr/lib/python3/dist-packages/django/core/checks/security/csrf.py�_csrf_middlewarer s � �6�(�:M�M�Mr T)�deployc �6 � t � � }|rg nt gS �N)r �W003��app_configs�kwargs�passed_checks r �check_csrf_middlewarer s � �#�%�%�L��)�2�2�D�6�)r c �h � t j pt � � pt j }|rg nt gS r )r �CSRF_USE_SESSIONSr �CSRF_COOKIE_SECURE�W016r s r �check_csrf_cookie_securer # s>