Psr-7
2 likes•1,341 views
PSR-7 defines common interfaces for HTTP messages to promote interoperability between PHP HTTP clients and servers. It models HTTP messages as objects with properties and methods for headers, bodies, status codes, and more. This provides a standardized way for frameworks, libraries, and applications to consume and generate HTTP requests and responses.
![URI
SCHEME://AUTHORITY[/PATH][?QUERY
STRING]
AUTHORITY = [USER[:PASS]@]HOST[:PORT]](https://image.slidesharecdn.com/psr-7-150317032759-conversion-gate01/85/Psr-7-7-320.jpg)
![HEADERS
/* Returns the following structure:
[
'Header' => [
'value1'
'value2'
]
]
*/
foreach ($message>getAllHeaders() as $header => $values) {
}](https://image.slidesharecdn.com/psr-7-150317032759-conversion-gate01/85/Psr-7-26-320.jpg)
![URI INTERFACE
URI are treated as value objects
// URI parts:
$scheme = $uri>getScheme();
$userInfo = $uri>getUserInfo();
$host = $uri>getHost();
$port = $uri>getPort();
$path = $uri>getPath();
$query = $uri>getQuery(); // the query STRING
$authority = $uri>getAuthority(); // [userinfo@]host[:port]
$uri = $uri
>withScheme('http')
>withHost('example.com')
>withPath('/foo/bar')
>withQuery('?baz=bat');](https://image.slidesharecdn.com/psr-7-150317032759-conversion-gate01/85/Psr-7-32-320.jpg)
Psr-7
- 1. PSR-7 A SET OF COMMON INTERFACES FOR HTTP MESSAGES by Marco Perone / @marcoshuttle
- 4. BODY string handled by server and clients as a stream PHP natively represents it using streams
- 5. REQUEST MESSAGE LINE METHOD REQUEST-TARGET HTTP/VERSION
- 6. REQUEST TARGET origin form absolute form authority form asterisk form
- 8. RESPONSE MESSAGE LINE HTTP/VERSION STATUS REASON
- 9. USE OF HTTP MESSAGES IN PHP
- 10. USE CASE 1 USE PHP SUPERGLOBALS Any application before frameworks
- 11. USE CASE 2 CREATE NEW IMPLEMENTATION FROM SCRATCH Frameworks define http components Single purpose libraries (oauth-server-php) Http clients ad Guzzle and Buzz
- 12. USE CASE 3 REQUIRE A SPECIFIC HTTP CLIENT/SERVER LIBRARY PROVIDING MESSAGE IMPLEMENTATION Silex, Stack, Drupal 8 have hard dependencies on Symfony's HTTP kernel Any SDK developed with Guzzle has a hard requirement on Guzzle's HTTP message implementations
- 13. USE CASE 4 CREATE ADAPTERS FOR COMMON HTTP MESSAGE IMPLEMENTATIONS Projects such as Geocoder create redundant adapters for common libraries
- 14. PROBLEMS Superglobals are mutable. Libraries can alter state of the application Unit and integration testing difficult Projects not capable of interoperability or cross- pollination Necessity of building a bridge layer between applications Any content emitted before a call to header()will result in that a call becoming a no-op
- 15. THE SCOPE OF PSR-7
- 16. GOALS Provide the interfaces needed for describing HTTP messages Focus on practical applications and usability Define the interfaces to model all elements of the HTTP message and URI specifications Ensure that the API does not impose arbitrary limits on HTTP messages Provide useful abstractions both for handling incoming requests for server-side applications and for sending outgoing requests in HTTP clients
- 17. NON GOALS Does not expect all HTTP client libraries or server-side frameworks to change their interfaces to conform. It is strictly meant for interoperability Should not impose implementation details
- 18. USE CASES
- 19. CLIENTS Unified message interface to use for making requests $response = $client>send($request);
- 20. MIDDLEWARES Function that accepts request and response as parameters and does something with them, including delegating to the next middleware function ( ServerRequestInterface $request, ResponseInterface $response, callable $next = null ) { # do stuff here }
- 21. FRAMEWORKS They did HTTP message abstraction since a long time PSR-7 provides a common set of interfaces Consider ZendStdlibDispatchableInterfacein Zend Framework 2 use ZendHttpRequestInterface; use ZendHttpResponseInterface; interface DispatchableInterface { public function dispatch( RequestInterface $request, ResponseInterface $response ); }
- 23. INTERMEZZO: VALUE OBJECTS Messages and URIs are modeled as value objects a change to any aspect of the message is essentially a new message immutability ensure integrity of message state use a base instance as prototype
- 28. BODIES treated as streams StreamableInterfaceis used $body = new Stream('php://temp'); $body>write('Here is the content for my message!'); $message = $message>withBody(new Stream('php://temp'));
- 31. REQUEST TARGET AND URI The request interface: composes a UriInterfaceinstance, which models the URI itself provides two methods around request-targets: getRequestTarget()and withRequestTarget()
- 32. URI INTERFACE URI are treated as value objects // URI parts: $scheme = $uri>getScheme(); $userInfo = $uri>getUserInfo(); $host = $uri>getHost(); $port = $uri>getPort(); $path = $uri>getPath(); $query = $uri>getQuery(); // the query STRING $authority = $uri>getAuthority(); // [userinfo@]host[:port] $uri = $uri >withScheme('http') >withHost('example.com') >withPath('/foo/bar') >withQuery('?baz=bat');
- 34. SERVER SIDE REQUESTS PHP's Server API does a number of things for us: Deserialization of query string arguments ($_GET) Deserialization of urlencoded form data submitted via POST ($_POST) Deserialization of cookies ($_COOKIE) Identification and handling of file uploads ($_FILES) Encapsulation of CGI/SAPI parameters ($_SERVER)
- 35. SERVER SIDE REQUESTS ServerRequestInterfaceextends the base RequestInterfaceand offers features around these values $query = $request>getQueryParams(); $body = $request>getParsedBody(); $cookies = $request>getCookieParams(); $files = $request>getFileParams(); $server = $request>getServerParams();
- 37. REFERENCES
- 38. by FIG PSR-7 metadocument FIG PSR-7 specifications PSR-7 by example @mwop