Our great sponsors
-
-
http-message
The purpose of this PSR is to provide a set of common interfaces for HTTP messages as described in RFC 7230 and RFC 7231
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
A while back I created a set of test traits to test & compare popular implementations of PSR-7. https://github.com/hamlet-framework/http-message-spec
This: https://www.php-fig.org/psr/psr-7/ Here's for example the set of tests that check the handling of host header:
NOTE:
The number of mentions on this list indicates mentions on common posts plus user suggested alternatives.
Hence, a higher number means a more popular project.
Related posts
- FrankenPHP, an app server for PHP written in Go: worker mode, Early Hints support, real-time capabilities, automatic HTTPS & HTTP/3
- Legacy "Routing" with PHP 8.1
- PER Coding Style 1.0.0
- [OOP] Best practice in structuring class hierarchies. I would like an API request to contact 2 different platforms, each in (the same) 2 different ways (GET and POST). How should I structure my class hierarchy? Thanks :)
- How the PHP Middleware Pattern works and can easily be applied