Bug #93945
closed
Hey Bernhard,
are you running TYPO3 with composer or non-composer? With composer there might be ways to update guzzle to a later version or patch Guzzle dependencies.
Reading the link you sent, the issue was fixed with guzzle v7.2.0. For TYPO3 v9 and TYPO3 v10, we use Guzzle v6.4.1 when creating tarballs/zip files, as we are not able to update to Guzzle due to breaking changes in their packages.
For TYPO3 v11 we have fixed various issues to ship to the latest Guzzle version.
- Status changed from New to Needs Feedback
Hey Benni,
unfortunately it is a non composer install (not yet migrated). So I think the best way to go is to manually edit the files to get rid of it until I am on TYPO3 11. :(
- Status changed from Needs Feedback to Closed
Sorry to hear this, but yes, upgrading to TYPO3 v11 is unfortunately the most useful solution. If you're not using version control / git / composer, one dirty hack would be - of course - to fix the place in the guzzle source code to fix the issue there.
Also available in: Atom
PDF