B
    ©0H[ë  ã               @   sp   d dl mZ ddlmZmZmZ eddd�Zeddd�Zd	d
„ Zeej	dd�dd„ ƒZ
eej	dd�dd„ ƒZdS )é    )Úsettingsé   )Ú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               C   s
   dt jkS )Nz)django.middleware.csrf.CsrfViewMiddleware)r   Z
MIDDLEWARE© r   r   údC:\Users\HIRONO~1\AppData\Local\Temp\pip-install-6bm3nxem\django\django\core\checks\security\csrf.pyÚ_csrf_middleware   s    r
   T)Zdeployc             K   s   t ƒ }|rg S tgS )N)r
   ÚW003)Úapp_configsÚkwargsÚpassed_checkr   r   r	   Úcheck_csrf_middleware   s    r   c             K   s"   t jptƒ  pt j}|rg S tgS )N)r   ZCSRF_USE_SESSIONSr
   ZCSRF_COOKIE_SECUREÚW016)r   r   r   r   r   r	   Úcheck_csrf_cookie_secure!   s    r   N)Zdjango.confr   Ú r   r   r   r   r   r
   Úsecurityr   r   r   r   r   r	   Ú<module>   s   