Wala shell

Advanced PHP File Manager

Server IP: 127.0.0.1 | PHP Version: 8.3.30 | Domains Hosted: 54

Name	Size	Last Modified	Actions
📁 ..	-	2024-05-29 15:36
📄 faq.rst .. _faq: Frequently Asked Questions ========================== This part of the documentation answers common questions about Requests. Encoded Data? ------------- Requests automatically decompresses gzip-encoded responses, and does its best to decode response content to unicode when possible. When either the `brotli <https://pypi.org/project/Brotli/>`_ or `brotlicffi <https://pypi.org/project/brotlicffi/>`_ package is installed, requests also decodes Brotli-encoded responses. You can get direct access to the raw response (and even the socket), if needed as well. Custom User-Agents? ------------------- Requests allows you to easily override User-Agent strings, along with any other HTTP Header. See :ref:`documentation about headers <custom-headers>`. Why not Httplib2? ----------------- Chris Adams gave an excellent summary on `Hacker News <http://news.ycombinator.com/item?id=2884406>`_: httplib2 is part of why you should use requests: it's far more respectable as a client but not as well documented and it still takes way too much code for basic operations. I appreciate what httplib2 is trying to do, that there's a ton of hard low-level annoyances in building a modern HTTP client, but really, just use requests instead. Kenneth Reitz is very motivated and he gets the degree to which simple things should be simple whereas httplib2 feels more like an academic exercise than something people should use to build production systems[1]. Disclosure: I'm listed in the requests AUTHORS file but can claim credit for, oh, about 0.0001% of the awesomeness. 1. http://code.google.com/p/httplib2/issues/detail?id=96 is a good example: an annoying bug which affect many people, there was a fix available for months, which worked great when I applied it in a fork and pounded a couple TB of data through it, but it took over a year to make it into trunk and even longer to make it onto PyPI where any other project which required " httplib2" would get the working version. Python 3 Support? ----------------- Yes! Requests officially supports Python 3.8+ and PyPy. Python 2 Support? ----------------- No! As of Requests 2.28.0, Requests no longer supports Python 2.7. Users who have been unable to migrate should pin to `requests<2.28`. Full information can be found in `psf/requests#6023 <https://github.com/psf/requests/issues/6023>`_. It is highly recommended users migrate to Python 3.8+ now since Python 2.7 is no longer receiving bug fixes or security updates as of January 1, 2020. What are "hostname doesn't match" errors? ----------------------------------------- These errors occur when :ref:`SSL certificate verification <verification>` fails to match the certificate the server responds with to the hostname Requests thinks it's contacting. If you're certain the server's SSL setup is correct (for example, because you can visit the site with your browser) and you're using Python 2.7, a possible explanation is that you need Server-Name-Indication. `Server-Name-Indication`_, or SNI, is an official extension to SSL where the client tells the server what hostname it is contacting. This is important when servers are using `Virtual Hosting`_. When such servers are hosting more than one SSL site they need to be able to return the appropriate certificate based on the hostname the client is connecting to. Python 3 already includes native support for SNI in their SSL modules. .. _`Server-Name-Indication`: https://en.wikipedia.org/wiki/Server_Name_Indication .. _`virtual hosting`: https://en.wikipedia.org/wiki/Virtual_hosting	3.55 KB	2024-05-29 15:36
📄 out-there.rst Integrations ============ Articles & Talks ================ - `Daniel Greenfeld's Review of Requests <https://pydanny.blogspot.com/2011/05/python-http-requests-for-humans.html>`_ - `Issac Kelly's 'Consuming Web APIs' talk <https://issackelly.github.io/Consuming-Web-APIs-with-Python-Talk/slides/slides.html>`_ - `Blog post about Requests via Yum <https://arunsag.wordpress.com/2011/08/17/new-package-python-requests-http-for-humans/>`_ - `Russian blog post introducing Requests <https://habr.com/post/126262/>`_ - `Sending JSON in Requests <http://www.coglib.com/~icordasc/blog/2014/11/sending-json-in-requests.html>`_	620 B	2024-05-29 15:36
📄 recommended.rst .. _recommended: Recommended Packages and Extensions =================================== Requests has a great variety of powerful and useful third-party extensions. This page provides an overview of some of the best of them. Certifi CA Bundle ----------------- `Certifi`_ is a carefully curated collection of Root Certificates for validating the trustworthiness of SSL certificates while verifying the identity of TLS hosts. It has been extracted from the Requests project. .. _Certifi: https://github.com/certifi/python-certifi CacheControl ------------ `CacheControl`_ is an extension that adds a full HTTP cache to Requests. This makes your web requests substantially more efficient, and should be used whenever you're making a lot of web requests. .. _CacheControl: https://cachecontrol.readthedocs.io/en/latest/ Requests-Toolbelt ----------------- `Requests-Toolbelt`_ is a collection of utilities that some users of Requests may desire, but do not belong in Requests proper. This library is actively maintained by members of the Requests core team, and reflects the functionality most requested by users within the community. .. _Requests-Toolbelt: https://toolbelt.readthedocs.io/en/latest/index.html Requests-Threads ---------------- `Requests-Threads`_ is a Requests session that returns the amazing Twisted's awaitable Deferreds instead of Response objects. This allows the use of ``async``/``await`` keyword usage on Python 3, or Twisted's style of programming, if desired. .. _Requests-Threads: https://github.com/requests/requests-threads Requests-OAuthlib ----------------- `requests-oauthlib`_ makes it possible to do the OAuth dance from Requests automatically. This is useful for the large number of websites that use OAuth to provide authentication. It also provides a lot of tweaks that handle ways that specific OAuth providers differ from the standard specifications. .. _requests-oauthlib: https://requests-oauthlib.readthedocs.io/en/latest/ Betamax ------- `Betamax`_ records your HTTP interactions so the NSA does not have to. A VCR imitation designed only for Python-Requests. .. _betamax: https://github.com/betamaxpy/betamax	2.12 KB	2024-05-29 15:36
📄 release-process.rst Release Process and Rules ========================= .. versionadded:: v2.6.2 Starting with the version to be released after ``v2.6.2``, the following rules will govern and describe how the Requests core team produces a new release. Major Releases -------------- A major release will include breaking changes. When it is versioned, it will be versioned as ``vX.0.0``. For example, if the previous release was ``v10.2.7`` the next version will be ``v11.0.0``. Breaking changes are changes that break backwards compatibility with prior versions. If the project were to change the ``text`` attribute on a ``Response`` object to a method, that would only happen in a Major release. Major releases may also include miscellaneous bug fixes. The core developers of Requests are committed to providing a good user experience. This means we're also committed to preserving backwards compatibility as much as possible. Major releases will be infrequent and will need strong justifications before they are considered. Minor Releases -------------- A minor release will not include breaking changes but may include miscellaneous bug fixes. If the previous version of Requests released was ``v10.2.7`` a minor release would be versioned as ``v10.3.0``. Minor releases will be backwards compatible with releases that have the same major version number. In other words, all versions that would start with ``v10.`` should be compatible with each other. Hotfix Releases --------------- A hotfix release will only include bug fixes that were missed when the project released the previous version. If the previous version of Requests released ``v10.2.7`` the hotfix release would be versioned as ``v10.2.8``. Hotfixes will not include upgrades to vendored dependencies after ``v2.6.2`` Reasoning --------- In the 2.5 and 2.6 release series, the Requests core team upgraded vendored dependencies and caused a great deal of headaches for both users and the core team. To reduce this pain, we're forming a concrete set of procedures so expectations will be properly set.	2.02 KB	2024-05-29 15:36
📄 support.rst .. _support: Support ======= If you have questions or issues about Requests, there are several options: Stack Overflow -------------- If your question does not contain sensitive (possibly proprietary) information or can be properly anonymized, please ask a question on `Stack Overflow <https://stackoverflow.com/questions/tagged/python-requests>`_ and use the tag ``python-requests``. File an Issue ------------- If you notice some unexpected behaviour in Requests, or want to see support for a new feature, `file an issue on GitHub <https://github.com/psf/requests/issues>`_. Send a Tweet ------------ If your question is less than 280 characters, feel free to send a tweet to `@nateprewitt <https://twitter.com/nateprewitt>`_, `@sethmlarson <https://twitter.com/sethmlarson>`_, or `@sigmavirus24 <https://twitter.com/sigmavirus24>`_.	846 B	2024-05-29 15:36
📄 updates.rst .. _updates: Community Updates ================= If you'd like to stay up to date on the community and development of Requests, there are several options: GitHub ------ The best way to track the development of Requests is through `the GitHub repo <https://github.com/psf/requests>`_. .. include:: ../../HISTORY.md	322 B	2024-05-29 15:36
📄 vulnerabilities.rst Vulnerability Disclosure ======================== If you think you have found a potential security vulnerability in requests, please email `Nate <mailto:nate.prewitt@gmail.com>`_ and `Seth <mailto:@sethmichaellarson@gmail.com>`_ directly. Do not file a public issue. Our PGP Key fingerprints are: - 8722 7E29 AD9C FF5C FAC3 EA6A 44D3 FF97 B80D C864 (`@nateprewitt <https://keybase.io/nateprewitt>`_) - EDD5 6765 A9D8 4653 CBC8 A134 51B0 6736 1740 F5FC (`@sethmlarson <https://keybase.io/sethmlarson>`_) You can also contact us on `Keybase <https://keybase.io/>`_ with the profiles above if desired. If English is not your first language, please try to describe the problem and its impact to the best of your ability. For greater detail, please use your native language and we will try our best to translate it using online services. Please also include the code you used to find the problem and the shortest amount of code necessary to reproduce it. Please do not disclose this to anyone else. We will retrieve a CVE identifier if necessary and give you full credit under whatever name or alias you provide. We will only request an identifier when we have a fix and can publish it in a release. We will respect your privacy and will only publicize your involvement if you grant us permission. Process ------- This following information discusses the process the requests project follows in response to vulnerability disclosures. If you are disclosing a vulnerability, this section of the documentation lets you know how we will respond to your disclosure. Timeline ~~~~~~~~ When you report an issue, one of the project members will respond to you within two days at the outside. In most cases responses will be faster, usually within 12 hours. This initial response will at the very least confirm receipt of the report. If we were able to rapidly reproduce the issue, the initial response will also contain confirmation of the issue. If we are not, we will often ask for more information about the reproduction scenario. Our goal is to have a fix for any vulnerability released within two weeks of the initial disclosure. This may potentially involve shipping an interim release that simply disables function while a more mature fix can be prepared, but will in the vast majority of cases mean shipping a complete release as soon as possible. Throughout the fix process we will keep you up to speed with how the fix is progressing. Once the fix is prepared, we will notify you that we believe we have a fix. Often we will ask you to confirm the fix resolves the problem in your environment, especially if we are not confident of our reproduction scenario. At this point, we will prepare for the release. We will obtain a CVE number if one is required, providing you with full credit for the discovery. We will also decide on a planned release date, and let you know when it is. This release date will always be on a weekday. At this point we will reach out to our major downstream packagers to notify them of an impending security-related patch so they can make arrangements. In addition, these packagers will be provided with the intended patch ahead of time, to ensure that they are able to promptly release their downstream packages. Currently the list of people we actively contact ahead of a public release is: - Python Maintenance Team, Red Hat (python-maint@redhat.com) - Daniele Tricoli, Debian (@eriol) We will notify these individuals at least a week ahead of our planned release date to ensure that they have sufficient time to prepare. If you believe you should be on this list, please let one of the maintainers know at one of the email addresses at the top of this article. On release day, we will push the patch to our public repository, along with an updated changelog that describes the issue and credits you. We will then issue a PyPI release containing the patch. At this point, we will publicise the release. This will involve mails to mailing lists, Tweets, and all other communication mechanisms available to the core team. We will also explicitly mention which commits contain the fix to make it easier for other distributors and users to easily patch their own versions of requests if upgrading is not an option. Previous CVEs ------------- - Fixed in 2.20.0 - `CVE 2018-18074 <https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-18074>`_ - Fixed in 2.6.0 - `CVE 2015-2296 <https://cve.mitre.org/cgi-bin/cvename.cgi?name=2015-2296>`_, reported by Matthew Daley of `BugFuzz <https://bugfuzz.com/>`_. - Fixed in 2.3.0 - `CVE 2014-1829 <https://cve.mitre.org/cgi-bin/cvename.cgi?name=2014-1829>`_ - `CVE 2014-1830 <https://cve.mitre.org/cgi-bin/cvename.cgi?name=2014-1830>`_	4.64 KB	2024-05-29 15:36

Terminal