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
In v2, the default the default behaviour of the ServerRequestyFActory was to return a request object, where you could get the contents of the body multiple times. in v3, every new read of getContents() will result in an empty string. (Casting the body to a string still works as before).
Since the way it currently works is correct according to PSR implementation, it should probably be updated in the migration guide. And it should not be changed back to the v2 implementation
Previous behavior
getBody->getContents would return the full stream every time
Current behavior
getBody->getContents will return the full stream the first time, and then an empty string on consecutive calls.
How to reproduce
Send a post request and call request->getBody()->getContents() multiple times.
The text was updated successfully, but these errors were encountered:
BC Break Report
Summary
In v2, the default the default behaviour of the
ServerRequestyFActory
was to return a request object, where you could get the contents of the body multiple times. in v3, every new read of getContents() will result in an empty string. (Casting the body to a string still works as before).Since the way it currently works is correct according to PSR implementation, it should probably be updated in the migration guide. And it should not be changed back to the v2 implementation
Previous behavior
getBody->getContents would return the full stream every time
Current behavior
getBody->getContents will return the full stream the first time, and then an empty string on consecutive calls.
How to reproduce
Send a post request and call request->getBody()->getContents() multiple times.
The text was updated successfully, but these errors were encountered: