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 (by php-fig)
per-coding-style
PER coding style (by php-fig)
| http-message | per-coding-style | |
|---|---|---|
| 17 | 10 | |
| 6,909 | 249 | |
| 0.2% | 0.8% | |
| 2.4 | 7.6 | |
| 8 months ago | about 1 month ago | |
| PHP | ||
| MIT License | - |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
http-message
Posts with mentions or reviews of http-message.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-11-29.
-
Testing an OpenAPI specification in PHP
There is a package within The PHP League that allows validation of an OpenAPI specification: league/openapi-psr7-validator. This package validates requests and responses to the PSR-7 specification.
-
How to use PSR HTTP standards to upgrade your code
PSR-7, the standard for requests and responses
-
Need some advice. Which is better? Guzzle or cURL?
Guzzle implements PSR-7: HTTP message interfaces (but apparently not yet PSR-18: HTTP Client, or at least they don't mention it). That means it's possible to use it in third-party libraries/frameworks and easy to replace with similar tools.
-
Creating an application #8 - application
The Yii HTTP Application provides the Application::class, as well as the events and handlers needed to interact with HTTP. The package is implemented using PSR-7 and PSR-15 standards.
-
Creating an application #1 - introduction
[PSR Http Message.](https://github.com/php-fig/http-message) This repository holds all interfaces/classes/traits related to [PSR-7](http://www.php-fig.org/psr/psr-7/).
-
Creating an application in Yii3.
PSR Http Message. This repository holds all interfaces/classes/traits related to PSR-7.
-
The PHPer's Guide to OAuth
Since the library is designed to be easily integrated with different frameworks, it relies on the usage of PSR-7 compliant HTTP messages. To fulfill this requirement, I'll be using the nyholm/psr7 package.
-
FrankenPHP, an app server for PHP written in Go: worker mode, Early Hints support, real-time capabilities, automatic HTTPS & HTTP/3
Sounds good for the future given that PHP-FIG seems uninterested in maintaining the related code repo https://github.com/php-fig/http-message/pull/95
- Legacy "Routing" with PHP 8.1
- Decorator pattern implementing interface
per-coding-style
Posts with mentions or reviews of per-coding-style.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-04-05.
- Using PER Coding Style with Laravel Pint
-
Per Coding Style 2.0
We discussed this: https://github.com/php-fig/per-coding-style/issues/25
-
About the lack of code styling guides for array functions (map, reduce, filter)
PSR-12 is being replaced by PER-Coding Style: https://github.com/php-fig/per-coding-style
-
PER Coding Style 1.0.0
Version 1.0.0 is a fully compatible copy of PSR-12. You can and should start saying "Coding Style PER" wherever you previously would say "PSR-12". Version 2.0.0 (Or whatever the next version ends up being) will include all new language features being tracked here and whatever else comes up in the meantime. This is something I'm hoping to have done by the end of the year, preferably by the release of PHP 8.2 but in my experience it can take a long time to reach consensus on these types of things and it's important that we get things as "right" as possible.
- Laravel Best Practices for Developers | 2022
What are some alternatives?
When comparing http-message and per-coding-style you can also consider the following projects:
L5-Swagger - OpenApi or Swagger integration to Laravel
Cake Validation - [READ-ONLY] Validation library from CakePHP. This repo is a split of the main code that can be found in https://github.com/cakephp/cakephp
Nyholm PSR-7 - A super lightweight PSR-7 implementation
console - Eases the creation of beautiful and testable command line interfaces
PHP Dotenv - Loads environment variables from `.env` to `getenv()`, `$_ENV` and `$_SERVER` automagically.
PHP OAuth 2.0 Server - A spec compliant, secure by default PHP OAuth 2.0 Server
HTTPFul - A Chainable, REST Friendly, PHP HTTP Client. A sane alternative to cURL.
http-structured-fields - Structured Field Values for HTTP manipulation in PHP
skeleton - A skeleton repository for League Packages
user-documentation - Documentation for those that use HHVM and write Hack code.
http-server-handler - Interface for PSR-15 server request handler
Requests - Requests for PHP is a humble HTTP request library. It simplifies how you interact with other sites and takes away all your worries.
http-message vs L5-Swagger
per-coding-style vs Cake Validation
http-message vs Nyholm PSR-7
http-message vs console
http-message vs PHP Dotenv
http-message vs PHP OAuth 2.0 Server
http-message vs HTTPFul
http-message vs http-structured-fields
http-message vs skeleton
http-message vs user-documentation
http-message vs http-server-handler
http-message vs Requests