>i'"ddlmZddlZddlZddlmZmZmZm Z ddl m Z er ddl m Z ddlmZej eZeddZGd d Zy) ) annotationsN) TYPE_CHECKINGAnyOptionalUnion) HTTPError) HeaderEntry) CookieParamiceZdZdZ d ddZeddZeddZeddZeddZ eddZ edd Z edd Z edd Z dd Zdd Zy)ResponseanHTTP response object for browser-based fetch requests. This class provides a standardized interface for handling HTTP responses obtained through the browser's fetch API. It mimics the requests.Response interface while preserving all browser-specific metadata including cookies, headers, and network timing information. Key Features: - Compatible with requests.Response API for easy migration - Preserves both request and response headers for analysis - Automatic cookie extraction from Set-Cookie headers - Lazy JSON parsing with caching - Browser-context aware (respects CORS, security policies) - Content available in multiple formats (text, bytes, JSON) The response contains all data captured during the browser's fetch execution, including redirects, authentication flows, and any browser-applied transformations. Nc 4||_||_||_||_|xsg|_|xsg|_|xsg|_||_|tv|_ tjd|d|dt|jdt|j y)aInitialize a new Response instance with browser fetch results. Args: status_code: HTTP status code returned by the server (e.g., 200, 404, 500). content: Raw response body as bytes. Used for binary data or when text encoding is uncertain. text: Response body as decoded string. Pre-decoded by browser's fetch API. json: Pre-parsed JSON data if response Content-Type was application/json. If None, json() method will attempt to parse from text on demand. response_headers: Headers received from the server, including Set-Cookie, Content-Type, and any custom headers sent by the server. request_headers: Headers that were actually sent in the request, including browser-generated headers (User-Agent, Accept, etc.) and custom headers. cookies: Cookies extracted from Set-Cookie headers during the response. These represent new/updated cookies from this specific request. url: Final URL after any redirects. May differ from original request URL if the server performed redirects during the request. zResponse initialized: status=, url=z , headers=z , cookies=N) _status_code_content_text_json_response_headers_request_headers_cookies_urlSTATUS_CODE_RANGE_OK_okloggerdebuglen) self status_codecontenttextjsonresponse_headersrequest_headerscookiesurls f/var/www/python/tenders/Scrapper/venv/lib/python3.12/site-packages/pydoll/browser/requests/response.py__init__zResponse.__init__&s:(   !1!7R / 52 2  "66 +K=seD41123:c$-->P=Q S c|jS)a>Check if the request was successful (2xx status codes). Returns: True if status code is in the 200-399 range, False otherwise. Note: This follows HTTP conventions where 2xx codes indicate success and 3xx codes indicate redirection (still considered "ok"). )rrs r&okz Response.okQs xxr(c|jS)aGet cookies that were set by the server during this response. Returns: List of cookies extracted from Set-Cookie headers. Each cookie contains name and value, with cookie attributes (Path, Domain, etc.) automatically handled by the browser. Note: These are only NEW/UPDATED cookies from this response. Existing browser cookies are managed automatically by the browser context. )rr*s r&r$zResponse.cookies^s}}r(c|jS)aGet headers that were actually sent in the HTTP request. Returns: List of headers sent to the server, including both custom headers provided by the user and automatic headers added by the browser (User-Agent, Accept, Authorization, etc.). Note: This shows the ACTUAL headers sent, which may differ from what was originally specified due to browser modifications. )rr*s r&r#zResponse.request_headersms$$$r(c|jS)aGet headers received from the server in the HTTP response. Returns: List of response headers sent by the server, including standard headers (Content-Type, Content-Length, etc.) and any custom headers. Note: Some security-sensitive headers may be filtered by the browser and not appear in this list due to CORS policies. )rr*s r&headerszResponse.headers|s%%%r(c|jS)zGet the HTTP status code returned by the server. Returns: Integer status code (e.g., 200 for OK, 404 for Not Found, 500 for Server Error). )rr*s r&rzResponse.status_codes   r(c|js.|jr"|jjdd|_|jS)aZGet the response content as a decoded string. Returns: Response body decoded as UTF-8 string. If no text was provided during initialization, it will be decoded from the raw content. Note: Decoding uses 'replace' error handling to avoid crashes on invalid UTF-8 sequences. zutf-8replace)errors)rrdecoder*s r&r z Response.texts6zzdll,,WY,GDJzzr(c|jS)zGet the raw response content as bytes. Returns: Unmodified response body as bytes. Useful for binary data (images, files, etc.) or when you need to handle encoding manually. )rr*s r&rzResponse.contents}}r(c|jS)zGet the final URL of the response after any redirects. Returns: The final URL that was accessed, which may differ from the original request URL if redirects occurred. )rr*s r&r%z Response.urlsyyr(c |j |jS tj|j|_|jS#tj$r&}t j dtd|d}~wwxYw)a~Parse and return the response content as JSON data. Attempts to parse the response text as JSON. Uses caching to avoid re-parsing the same content multiple times. Returns: Parsed JSON data as dictionary, list, or other JSON-compatible type. Raises: ValueError: If the response content is not valid JSON or if parsing fails. Note: - Uses lazy parsing: JSON is only parsed when first accessed - Subsequent calls return cached result for better performance - If JSON was pre-parsed during initialization, that result is returned Nz!Failed to decode response as JSONzResponse is not valid JSON)rjsonlibloadsr JSONDecodeErrorrr ValueError)rexcs r&r!z Response.jsonso" :: !::  D tyy1DJ:: && D LL< =9: C Ds/A B!A>>Bc|jtvrStjd|jd|jt |jd|jy)aRaise an HTTPError if the response indicates an HTTP error status. Checks the status code and raises an exception for client errors (4xx) and server errors (5xx). Successful responses (2xx) and redirects (3xx) do not raise an exception. Raises: HTTPError: If status code is 400 or higher, indicating an error. Note: This method is compatible with requests.Response.raise_for_status() for easy migration from the requests library. z&HTTP error status encountered: status=rz Client Error: for url N)rrrerrorrrr*s r&raise_for_statuszResponse.raise_for_statussg   #7 7 LL89I9I8J&QUQZQZP[\ t//00G {ST T 8r()r(NNNNr@)rintrbytesr strr!zOptional[dict[str, Any]]r"Optional[list[HeaderEntry]]r#rDr$zOptional[list[CookieParam]]r%rC)returnbool)rEzlist[CookieParam])rEzlist[HeaderEntry])rErA)rErC)rErB)rEzUnion[dict[str, Any], list])rENone)__name__ __module__ __qualname____doc__r'propertyr+r$r#r/rr rr%r!r?r(r&r r s,)-8<7;/3) ) )  ) ' ) 6 ) 5) -) ) V     % % & &!!  D6Ur(r ) __future__rr!r8loggingtypingrrrrpydoll.exceptionsrpydoll.protocol.fetch.typesr pydoll.protocol.network.typesr getLoggerrHrrangerr rMr(r&rVsL"66'79   8 $S#RURUr(