| Server IP : 178.105.222.151 / Your IP : 216.73.216.38 Web Server : nginx/1.28.3 System : Linux MNK 7.0.0-15-generic #15-Ubuntu SMP PREEMPT_DYNAMIC Wed Apr 22 16:06:43 UTC 2026 x86_64 User : www-data ( 33) PHP Version : 8.5.4 Disable Function : NONE MySQL : OFF | cURL : ON | WGET : ON | Perl : ON | Python : OFF | Sudo : ON | Pkexec : OFF Directory : /usr/lib/python3/dist-packages/botocore/__pycache__/ |
Upload File : |
+
��i�� � �� � R t ^ RIt^ RIt^ RIt^ RIt^ RIt^ RIt^ RIt^ RIt^ RI H
t
^ RIHt ^ RI
Ht ^ RIHt ^ RIHt ^ RIHtHtHtHt RtR tR
t]P6 ! R4 tRtR
t]]3tR]3R lt ! R R4 t! ! R R]!4 t" ! R R]"4 t# ! R R]!4 t$ ! R R]!4 t% ! R R]!4 t& ! R R]!4 t' ! R R]&]$4 t( ! R R!]&4 t) ! R" R#]']%4 t*R$]#R%]"R&]$R'](R(])R)]*/t+R# )*a� Protocol input serializes.
This module contains classes that implement input serialization
for the various AWS protocol types.
These classes essentially take user input, a model object that
represents what the expected input should look like, and it returns
a dictionary that contains the various parts of a request. A few
high level design decisions:
* Each protocol type maps to a separate class, all inherit from
``Serializer``.
* The return value for ``serialize_to_request`` (the main entry
point) returns a dictionary that represents a request. This
will have keys like ``url_path``, ``query_string``, etc. This
is done so that it's a) easy to test and b) not tied to a
particular HTTP library. See the ``serialize_to_request`` docstring
for more details.
Unicode
-------
The input to the serializers should be text (str/unicode), not bytes,
with the exception of blob types. Those are assumed to be binary,
and if a str/unicode type is passed in, it will be encoded as utf-8.
N)�ElementTree)�validate)�
formatdate)�ParamValidationError)�register_feature_id)�
has_header�is_json_value_header�parse_to_aware_datetime�percent_encode�iso8601z%Y-%m-%dT%H:%M:%SZz%Y-%m-%dT%H:%M:%S.%fZz^[A-Za-z0-9\.\-]+$�default�millisecondTc � � \ V , ! VR7 pV'