OwlCyberSecurity - MANAGER
Edit File: heuristics.cpython-36.pyc
3 �Pf- � @ s� d dl Z d dlZd dlmZmZmZ d dlmZmZ dZddd�Z dd� Z G d d � d e �Z G d d � d e �Z G d d� de �ZG dd� de �ZdS )� N)� formatdate� parsedate� parsedate_tz)�datetime� timedeltaz%a, %d %b %Y %H:%M:%S GMTc C s |p t j� }|| S )N)r �now)�delta�date� r � /usr/lib/python3.6/heuristics.py� expire_after s r c C s t tj| j� ��S )N)r �calendar�timegmZ timetuple)Zdtr r r �datetime_to_header s r c @ s$ e Zd Zdd� Zdd� Zdd� ZdS )� BaseHeuristicc C s dS )a! Return a valid 1xx warning header value describing the cache adjustments. The response is provided too allow warnings like 113 http://tools.ietf.org/html/rfc7234#section-5.5.4 where we need to explicitly say response is over 24 hours old. z110 - "Response is Stale"r )�self�responser r r �warning s zBaseHeuristic.warningc C s i S )z�Update the response headers with any new headers. NOTE: This SHOULD always include some Warning header to signify that the response was cached by the client, not by way of the provided headers. r )r r r r r �update_headers! s z BaseHeuristic.update_headersc C s@ | j |�}|r<|jj|� | j|�}|d k r<|jjd|i� |S )N�Warning)r �headers�updater )r r Zupdated_headersZwarning_header_valuer r r �apply* s zBaseHeuristic.applyN)�__name__� __module__� __qualname__r r r r r r r r s r c @ s e Zd ZdZdd� ZdS )� OneDayCachezM Cache the response by providing an expires 1 day in the future. c C sR i }d|j krNt|j d �}ttdd�t|d d� � d�}t|�|d< d|d< |S ) N�expiresr � )Zdays� )r �publicz cache-control)r r r r r r )r r r r r r r r r ; s zOneDayCache.update_headersN)r r r �__doc__r r r r r r 6 s r c @ s( e Zd ZdZdd� Zdd� Zdd� ZdS ) � ExpiresAfterz; Cache **all** requests for a defined time period. c K s t f |�| _d S )N)r r )r �kwr r r �__init__L s zExpiresAfter.__init__c C s t | j�}t|�dd�S )Nr )r z cache-control)r r r )r r r r r r r O s zExpiresAfter.update_headersc C s d}|| j S )Nz:110 - Automatically cached for %s. Response might be stale)r )r r Ztmplr r r r V s zExpiresAfter.warningN)r r r r! r$ r r r r r r r" G s r" c @ s> e Zd ZdZedddddddd d d d g �Zd d� Zdd� ZdS )� LastModifieda� If there is no Expires header already, fall back on Last-Modified using the heuristic from http://tools.ietf.org/html/rfc7234#section-4.2.2 to calculate a reasonable value. Firefox also does something like this per https://developer.mozilla.org/en-US/docs/Web/HTTP/Caching_FAQ http://lxr.mozilla.org/mozilla-release/source/netwerk/protocol/http/nsHttpResponseHead.cpp#397 Unlike mozilla we limit this to 24-hr. �� �� �� �� i, i- i� i� i� i� i� c C s� |j }d|kri S d|kr*|d dkr*i S |j| jkr:i S d|ksJd|krNi S tjt|d ��}t|d �}|d ks||d kr�i S tj� }td|| �}|tj|� }tdt |d d ��}||kr�i S || } dtj t tj | ��iS ) Nr z cache-controlr r z last-modifiedr � � i i�Q ) r Zstatus� cacheable_by_default_statusesr r r r �time�max�minZstrftime�TIME_FMTZgmtime) r �respr r Z last_modifiedr Z current_ager Zfreshness_lifetimer r r r r k s* zLastModified.update_headersc C s d S )Nr )r r1 r r r r � s zLastModified.warningN)r r r r! �setr, r r r r r r r% [ s r% )N)r r- Z email.utilsr r r r r r0 r r �objectr r r" r% r r r r �<module> s "