2i dZddlZddlZddlZddlZddlmZddlmZddl m Z m Z ddl m Z dZdZd ZGd d e ZGd d e Zy)z0:py:class:`django.http.HttpResponse` subclasses.N)quote)settings) HttpResponseStreamingHttpResponse) force_strct|tr|jd}t|}t j d|}|j dd}|jd}tjdd|}|S)umReturn US-ASCII encoded ``value`` for Content-Disposition header. >>> print(encode_basename_ascii(u'éà')) ea Spaces are converted to underscores. >>> print(encode_basename_ascii(' ')) _ Of course, ASCII values are not modified. >>> print(encode_basename_ascii('ea')) ea >>> print(encode_basename_ascii(b'ea')) ea zutf-8NFKDasciiignorez[\s]_) isinstancebytesdecodestr unicodedata normalizeencoderesub)valueascii_basenames S/var/www/html/acx/venv/lib/python3.12/site-packages/django_downloadview/response.pyencode_basename_asciir sq&% W%ZN **6>BN#**7H=N#**73NVVGS.9N c*tt|S)uReturn UTF-8 encoded ``value`` for use in Content-Disposition header. >>> print(encode_basename_utf8(u' .txt')) %20.txt >>> print(encode_basename_utf8(u'éà')) %C3%A9%C3%A0 )rr)rs rencode_basename_utf8r*s 5! ""rcZ|syt|}t|}||k(rd|dSd|d|S)uReturn value of ``Content-Disposition`` header with 'attachment'. >>> print(content_disposition('demo.txt')) attachment; filename="demo.txt" If filename is empty, only "attachment" is returned. >>> print(content_disposition('')) attachment If filename contains non US-ASCII characters, the returned value contains UTF-8 encoded filename and US-ASCII fallback. >>> print(content_disposition(u'é.txt')) attachment; filename="e.txt"; filename*=UTF-8''%C3%A9.txt attachmentzattachment; filename=""z"; filename*=UTF-8'')rr)filenameascii_filename utf8_filenames rcontent_dispositionr#7sT$ *84N(2M&''7q99%^$45 - 0 rcheZdZdZ d fd ZedZfdZdZdZ dZ dZ d Z xZ S) DownloadResponsea>File download response (Django serves file, client downloads it). This is a specialization of :class:`django.http.StreamingHttpResponse` where :attr:`~django.http.StreamingHttpResponse.streaming_content` is a file wrapper. Constructor differs a bit from :class:`~django.http.response.HttpResponse`. Here are some highlights to understand internal mechanisms and motivations: * Let's start by quoting :pep:`3333` (WSGI specification): For large files, or for specialized uses of HTTP streaming, applications will usually return an iterator (often a generator-iterator) that produces the output in a block-by-block fashion. * Django WSGI handler (application implementation) returns response object (see :mod:`django.core.handlers.wsgi`). * :class:`django.http.HttpResponse` and subclasses are iterators. * In :class:`~django.http.StreamingHttpResponse`, the :meth:`~container.__iter__` implementation proxies to :attr:`~django.http.StreamingHttpResponse.streaming_content`. * In :class:`DownloadResponse` and subclasses, :attr:`streaming_content` is a :doc:`file wrapper `. File wrapper is itself an iterator over actual file content, and it also encapsulates access to file attributes (size, name, ...). c||_tt||j||||_||_|s|d=||_||_|jjD]\}} ||vs | ||<y)a=Constructor. :param content_type: Value for ``Content-Type`` header. If ``None``, then mime-type and encoding will be populated by the response (default implementation uses :mod:`mimetypes`, based on file name). )streaming_contentstatus content_type Content-TypeN) filesuperr%__init__basenamer file_mimetype file_encodingdefault_headersitems) self file_instancerr.r(r)r/r0headerr __class__s rr-zDownloadResponse.__init__xs("  ."ii\ / ! %^$ + +"11779 %MFET!$V  %rc> |jS#t$ri}|j|d< |jj|d<n#tt f$rYnwxYw|j r|j}t||d<||_|jcYSwxYw)amReturn dictionary of automatically-computed headers. Uses an internal ``_default_headers`` cache. Default values are computed if only cache hasn't been set. ``Content-Disposition`` header is encoded according to `RFC 5987 `_. See also http://stackoverflow.com/questions/93551/. r*zContent-LengthzContent-Disposition) _default_headersAttributeErrorget_content_typer+sizeNotImplementedErrorr get_basenamer#)r3headersr.s rr1z DownloadResponse.default_headerss )(( ( )G&*&;&;&=GN # ,0IINN()"$78  ,,.1DX1N-.$+D !(( ( )s3 BABABAABBc(tt| S)zReturn iterable of (header, value). This method is called by http handlers just before WSGI's start_response() is called... but it is not called by django.test.ClientHandler! :'( )r,r%r2)r3r6s rr2zDownloadResponse.itemss%t244rc|jr |jStjj|jjS)zReturn basename.)r.ospathr+namer3s rr=zDownloadResponse.get_basenames0 ==== 77##DIINN3 3rc |jjS#t$r&|jd|j cYSwxYw)z:Return a suitable "Content-Type" header for ``self.file``.z ; charset=)r+r)r9 get_mime_type get_charsetrDs rr:z!DownloadResponse.get_content_typesN K99)) ) K((*+:d6F6F6H5IJ J Ks,AAc|j |jSd}|j}tj|\}}|xs|S)zReturn mime-type of the file.zapplication/octet-stream)r/r= mimetypes guess_type)r3default_mime_typer. mime_typeencodings rrFzDownloadResponse.get_mime_typesO    )%% %6$$&'228< 8---rc|j |jS|j}tj|\}}|S)z%Return encoding of the file to serve.)r0r=rIrJ)r3r.rLrMs r get_encodingzDownloadResponse.get_encodingsB    )%% %$$&'228< 8rc"tjS)z(Return the charset of the file to serve.)rDEFAULT_CHARSETrDs rrGzDownloadResponse.get_charsets'''r)TNNNN)__name__ __module__ __qualname____doc__r-propertyr1r2r=r:rFrOrG __classcell__)r6s@rr%r%VsVH1%f))454K.(rr%ceZdZdZy)ProxiedDownloadResponsezBase class for internal redirect download responses. This base class makes it possible to identify several types of specific responses such as :py:class:`~django_downloadview.nginx.response.XAccelRedirectResponse`. N)rSrTrUrVrrrZrZsrrZ)rVrIrArr urllib.parser django.confr django.httprrdjango.utils.encodingrrrr#r%rZr[rrr`sK6  ;+: # >[(,[(|lr