Fixes #4656
We noticed that the run-server command constantly fails on our Travis build after upgrading to Drupal 10. After looking into the code, we found that the exceptions used in the checkUrl method is no longer respected in Guzzle 7 and causing a client error to be thrown when curl returns a 404 response .
The option was deprecated in Guzzle 6 and was removed in 7 according to this PR https://github.com/guzzle/guzzle/pull/2464 (I don't see the option being marked deprecated anywhere)
Proposed changes
Switch to use the new option http_errors. The option was introduced in Guzzle 6, so it should be safe to use without changing anything in the composer.json file as Guzzle 6 was the minimum version required by Drupal 9.
Motivation
Fixes #4656 We noticed that the run-server command constantly fails on our Travis build after upgrading to Drupal 10. After looking into the code, we found that the
exceptions
used in thecheckUrl
method is no longer respected in Guzzle 7 and causing a client error to be thrown when curl returns a 404 response .The option was deprecated in Guzzle 6 and was removed in 7 according to this PR https://github.com/guzzle/guzzle/pull/2464 (I don't see the option being marked deprecated anywhere)
Proposed changes
Switch to use the new option
http_errors
. The option was introduced in Guzzle 6, so it should be safe to use without changing anything in thecomposer.json
file as Guzzle 6 was the minimum version required by Drupal 9.Testing steps
blt tests:server:start -vvvv
.