Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[TASK] Use TYPO3 HTTP configuration in sentry client #104

Merged
merged 2 commits into from
Apr 22, 2024

Conversation

derhansen
Copy link
Contributor

With version 4 of the Sentry SDK, Sentry now ships a simple and custom HTTP client which is based on curl. Using Guzzle as HTTP client does not seem possible, since Sentry SDK does use php-http/discovery anymore.

Basic HTTP configuration in $GLOBALS['TYPO3_CONF_VARS']['HTTP'] should be reflected to the Sentry HTTP client.

This change reflects the following TYPO3 HTTP options to the Sentry HTTP client:

  • verify
  • http_timeout
  • connect_timeout

Closes #103

With version 4 of the Sentry SDK, Sentry now ships a simple
and custom HTTP client which is based on curl. Using Guzzle
as HTTP client does not seem possible, since Sentry SDK
does use `php-http/discovery` anymore.

Basic HTTP configuration in $GLOBALS['TYPO3_CONF_VARS']['HTTP']
should be reflected to the Sentry HTTP client.

This change reflects the following TYPO3 HTTP options to
the Sentry HTTP client:

* verify
* http_timeout
* connect_timeout

Closes networkteam#103
@christophlehmann christophlehmann merged commit 5978be6 into networkteam:main Apr 22, 2024
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[TASK] Refect TYPO3 HTTP options to Sentry HTTP client
2 participants