tl;dr: The new request extension provides server-side request and response objects for PHP 7. Use it as a replacement object for request superglobals and response functions. An equivalent PHP 5 version is available in userland as pmjones/request.
\nYou're tired of dealing with the $_GET, $_POST, etc. superglobals in your PHP 7 application. You wish $_FILES was easer to deal with. You'd prefer to wrap them all in an object to pass around to your class methods, so they'd be easier to test. And as long as they're all in an object, it might be nice to have parsed representations of the various incoming headers. Preferably, you'd like for it to be read-only, so that the various libraries you use can't modify superglobal state out from under you.
Likewise, seeing the \u201cCannot modify header information - headers already sent\u201d warning is getting on your nerves. You'd like to get away from using header(), setcookie(), and the rest. You know they're hard to inspect, and they're hard to test. What would be great is to have all that response work wrapped in another object that you can pass around, and inspect or modify it before sending the response back to the client.
You could maybe adopt a framework, but why do that for your custom project? Just a pair of server-side request and response objects would make your life so much easer. Why can't there be set of internal PHP classes for that?
\nWell, now there is. You can install the request extension from John Boehr and myself to get ServerRequest and ServerReponse objects as if PHP itself provided them.
After you install the extension, you can issue $request = new ServerRequest(), and then:
Instead of ... ... use:\n--------------------------------------- ---------------------------------------\n$_COOKIE $request->cookie\n$_ENV $request->env\n$_GET $request->get\n$_FILES $request->files\n$_POST $request->post\n$_SERVER $request->server\n$_SERVER['REQUEST_METHOD'] $request->method\n$_SERVER['HTTP_HEADER_NAME'] $request->headers['header-name']\nfile_get_contents('php://input') $request->content\n$_SERVER['HTTP_CONTENT_LENGTH'] $request->contentLength\n$_SERVER['HTTP_CONTENT_MD5'] $request->contentMd5\n$_SERVER['PHP_AUTH_PW'] $request->authPw\n$_SERVER['PHP_AUTH_TYPE'] $request->authType\n$_SERVER['PHP_AUTH_USER'] $request->authUser\nLikewise:
\nInstead of parsing ... ... use:\n--------------------------------------- ---------------------------------------\nisset($_SERVER['key']) $request->server['key'] ?? 'default'\n ? $_SERVER['key'] (good for all superglobals)\n : 'default';\n$_FILES to look more like $_POST $request->uploads\n$_SERVER['HTTP_CONTENT_TYPE'] $request->contentType and\n $request->contentCharset\n$_SERVER['HTTP_ACCEPT'] $request->accept\n$_SERVER['HTTP_ACCEPT_CHARSET'] $request->acceptCharset\n$_SERVER['HTTP_ACCEPT_ENCODING'] $request->acceptEncoding\n$_SERVER['HTTP_ACCEPT_LANGUAGE'] $request->acceptLanguage\n$_SERVER['HTTP_X_HTTP_METHOD_OVERRIDE'] $request->method\n$_SERVER['PHP_AUTH_DIGEST'] $request->authDigest\n$_SERVER['HTTP_X_REQUESTED_WITH'] $request->xhr\n == 'XmlHttpRequest'\nThose properties are all read-only, so there's no chance of them being changed without you knowing. (There are some true immutables for application-related values as well; see the documentation.)
\nFor responses, you can issue $response = new ServerResponse(), and then:
Instead of ... ... use:\n--------------------------------------- ---------------------------------------\nheader('Foo: bar', true); $response->setHeader('Foo', 'bar');\nheader('Foo: bar', false); $response->addHeader('Foo', 'bar');\nsetcookie('foo', 'bar'); $response->setCookie('foo', 'bar');\nsetrawcookie('foo', 'bar'); $response->setRawCookie('foo', 'bar');\necho $content; $response->setContent($content);\nYou can inspect the $response object, and then call $response->send() to
\nsend it to the client.
Working with JSON?
\n// instead of ...\nheader('Content-Type: application/json')\necho json_encode($value);\n\n// .. use:\n$response->setContentJson($value);\nSending a $file for download?
// instead of ...\nheader('Content-Type: application/octet-stream');\nheader('Content-Transfer-Encoding: binary');\nheader(\n 'Content-Disposition: attachment;filename=\"'\n . rawurlencode(basename($file)) . '\"'\n);\n$fh = fopen($file, 'rb+');\nfpasthru($fh);\n\n// use:\n$fh = fopen($file, 'rb+');\n$response->setContentDownload($fh, basename($file));\nBuilding a complex header? Pass an array instead of a string:
\n$response->setHeader('Cache-Control', [\n 'public',\n 'max-age' => '123',\n 's-maxage' => '456',\n 'no-cache',\n]); // Cache-Control: public, max-age=123, s-maxage=456, no-cache\n\n$response->setHeader('X-Whatever', [\n 'foo',\n 'bar' => [\n 'baz' => 'dib',\n 'zim',\n 'gir' => 'irk',\n ],\n 'qux' => 'quux',\n]); // X-Whatever: foo, bar;baz=dib;zim;gir=irk, qux=quux\nYou can read the rest of the documentation at https://gitlab.com/pmjones/ext-request to discover more convenient functionality. And if you're stuck on PHP 5.x for now, the extension has a userland version installable via Composer as pmjones/request.
\nTry out the request extension today, because a pair of server-side request and response objects will make your life a lot easier.