Join GitHub today
Implement an ErrorTransport #1529
When using AwsAuthV4 transport, it is possible that the user provides incorrect credentials.
This means that the Guzzle client will get a 403 from AWS.
By default Guzzle silently ignores all exceptions and stores them in
This feature allows a downstream client/library to handle them however.
Currently, FOSElastica does nothing to process 403 or other errors that come back from ruflin/Elastica (transferInfo is never used).
This causes a problem because 403 are silently ignored and the progress bar appears to be moving unhindered ;-)
This PR is a pre-requisite for unit tests that will accompany this fix on FOSElastica
@ruflin updated the PR and made the NullTransport more generic and testable
@Destroy666x added the support for non-403 error codes that you've requested
Matching PR FOSElasticaBundle in https://github.com/FriendsOfSymfony/FOSElasticaBundle/pull/1465/files
Will merge it as I can't see at the moment how it should break other things. Left one comment where any input is welcome.