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

Default datadog.appsec.enabled changed to on #242

Open
edsrzf opened this issue Apr 11, 2023 · 1 comment
Open

Default datadog.appsec.enabled changed to on #242

edsrzf opened this issue Apr 11, 2023 · 1 comment
Labels
bug Something isn't working

Comments

@edsrzf
Copy link

edsrzf commented Apr 11, 2023

Description

After release 0.7.0, datadog.appsec.enabled seems to default to On instead of off. I don't intend to use this extension and this change in defaults has caused problems for me when tracing is disabled. (See #241)

Explanation

The default for datadog.appsec.enabled depends on datadog.remote_config_enabled, which defaults to On. (See code here.) This means that datadog.appsec.enabled is now effectively on by default, as far as I can tell.

I believe this changed in #180, which was released with 0.7.0.

Installation

I don't intend to be using appsec. I install ddtrace using the recommended setup script:

curl -LO https://github.com/DataDog/dd-trace-php/releases/latest/download/datadog-setup.php
php datadog-setup.php --php-bin=all

I do not pass --enable-appsec, so I expect appsec to be disabled, since the docs state:

When you do not specify --enable-appsec, the AppSec extension loads shortly at startup, and is not enabled by default. It immediately short-circuits, causing negligible performance overhead.

@marcus-crane
Copy link

Related issue it seems: DataDog/dd-trace-php#2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants