You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was checking this PHP PR: php/php-src#11093 and I realized that in Symfony we have the opposite problem. Instead of "server software", we define the "client software" via the User Agent in several components.
… agents to comply with the RFC 9110 specification (javiereguiluz)
This PR was squashed before being merged into the 6.3 branch.
Discussion
----------
[BrowserKit][HttpClient] Update the value of some user agents to comply with the RFC 9110 specification
| Q | A
| ------------- | ---
| Branch? | 6.3
| Bug fix? | yes
| New feature? | no
| Deprecations? | no
| Tickets | fixes#50052
| License | MIT
| Doc PR | -
Commits
-------
722bd99 [BrowserKit][HttpClient] Update the value of some user agents to comply with the RFC 9110 specification
Description
I was checking this PHP PR: php/php-src#11093 and I realized that in Symfony we have the opposite problem. Instead of "server software", we define the "client software" via the User Agent in several components.
The User Agent format is defined in RFC 9110: https://www.rfc-editor.org/rfc/rfc9110.html#name-user-agent
And:
And a
token
in this context is:So, user agents can omit the version if they want, but the identifier can't contain spaces.
That's why I think we should update these user agents:
(1) Rename this one as
SymfonyBrowserKit
?symfony/src/Symfony/Component/BrowserKit/AbstractBrowser.php
Line 135 in 660ce12
(2) Rename this one as
SymfonyHttpClient (Amp)
?symfony/src/Symfony/Component/HttpClient/AmpHttpClient.php
Line 101 in 660ce12
(3) Rename this one as
SymfonyHttpClient (Curl)
?symfony/src/Symfony/Component/HttpClient/CurlHttpClient.php
Line 96 in 660ce12
(4) Rename this one as
SymfonyHttpClient (Native)
?symfony/src/Symfony/Component/HttpClient/NativeHttpClient.php
Line 194 in 660ce12
Thanks
Example
No response
The text was updated successfully, but these errors were encountered: