Pass verify option to GuzzleHttp\Client #38
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jepf
suggested changes
Mar 29, 2021
There was a problem hiding this comment.
Thank you for your pull request.
It seems that guzzle not only supports true and false for its verify option, but that also the path to a CA bundle file can be given: https://docs.guzzlephp.org/en/stable/request-options.html#verify
Would you mind to also add support for this file path?
|
Did implement the change, please review. |
jepf
approved these changes
Mar 29, 2021
|
Thank you. Merged and tagged release 2.0.2. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Allow to enable/disable ssl verify in zammad api client.