| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
…t_pii The url.full, url.path, and http.query span attributes can contain user-provided query parameters and paths that may include PII. Gate these behind the send_default_pii setting, consistent with how client.address is handled. Fixes PY-2552 Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Sorry, something went wrong.
Codecov Results 📊✅ 89867 passed | ⏭️ 6240 skipped | Total: 96107 | Pass Rate: 93.51% | Execution Time: 323m 58s 📊 Comparison with Base Branch
All tests are passing successfully. ✅ Patch coverage is 100.00%. Project has 2394 uncovered lines.
@@ Coverage Diff @@
## main #PR +/-##
==========================================
+ Coverage 89.88% 89.93% +0.05%
==========================================
Files 192 192 —
Lines 23763 23766 +3
Branches 8206 8208 +2
==========================================
+ Hits 21358 21372 +14
- Misses 2405 2394 -11
- Partials 1345 1342 -3Generated by Codecov Action |
Sorry, something went wrong.
| envelope = events[0] | ||
|
|
||
| assert envelope["type"] == "transaction" | ||
| assert envelope["transaction"] == "generic WSGI request" | ||
| assert envelope["contexts"]["trace"]["op"] == "http.server" | ||
| assert envelope["request"] == DictionaryContaining( | ||
| {"method": "GET", "url": "http://localhost/dogs/are/great/"} | ||
| { | ||
| "method": "GET", | ||
| "url": "http://localhost/dogs/are/great", | ||
| "query_string": "toy=tennisball", | ||
| } |
There was a problem hiding this comment.
Bug: The WSGI integration leaks PII in non-streaming transaction events by unconditionally adding url and query_string, even when send_default_pii is False.
Severity: HIGH
In the _make_wsgi_event_processor function, wrap the assignments for request_info["url"] and request_info["query_string"] in a conditional check for should_send_default_pii(). This will ensure that PII is consistently redacted across both streaming and non-streaming code paths, respecting the user's setting.
Prompt for AI AgentReview the code at the location below. A potential bug has been identified by an AI agent. Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not valid. Location: tests/integrations/wsgi/test_wsgi.py#L265-L276 Potential issue: The WSGI integration aims to prevent sending Personally Identifiable Information (PII) when `send_default_pii` is `False`. While the change correctly redacts PII for span attributes in the streaming path (`_get_request_attributes`), it fails to do so for the non-streaming transaction event path. The `_make_wsgi_event_processor` function unconditionally sets `request["url"]` and `request["query_string"]` on the event. This results in an inconsistent behavior where users who set `send_default_pii=False` will still have unredacted URLs and query strings sent in transaction events if they are not using the span streaming path, leading to an unintended PII leak.
Did we get this right? 👍 / 👎 to inform future reviews.
Sorry, something went wrong.
There was a problem hiding this comment.
I'm not convinced that not gating URL attribute behind send_default_pii is considered a sufficiently severe bug that allows us to break existing behavior.
I'll stamp given precedent in #6501.
Sorry, something went wrong.
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Want reviews to match your repository better? Bugbot Learning can learn team-specific rules from PR activity. A team admin can enable Learning in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 6273bbd. Configure here.
Sorry, something went wrong.
| if path: | ||
| attributes["url.path"] = path | ||
|
|
||
| attributes["url.full"] = get_request_url(environ, use_x_forwarded_for) |
There was a problem hiding this comment.
Medium Severity
When send_default_pii is enabled, url.path is taken from PATH_INFO only, while url.full is built with get_request_url, which merges SCRIPT_NAME and PATH_INFO. Mounted WSGI apps can therefore emit spans where url.path and url.full describe different paths.
Reviewed by Cursor Bugbot for commit 6273bbd. Configure here.
Sorry, something went wrong.
If we decide to talk about this more, we should make it a thread/convo with some other folks outside of this PR. One could argue that we were breaking the contract set out by our conventions/attributes by not doing so, and, in another case for a different attribute relatively recently, we considered it sufficiently severe that we called an incident over it to correct this. |
Sorry, something went wrong.
…6664) Gates `url.full`, `url.path`, and `url.query` span attributes in the Tornado integration behind `send_default_pii`, consistent with the same fix applied to the aiohttp (#6650) and wsgi (#6654) integrations. Adds a `send_pii` parametrize dimension to the transactions test to cover both the PII-on and PII-off paths explicitly. Fixes PY-2556 Fixes #6661 Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
…t_pii (getsentry#6654) The WSGI integration now gates `url.full`, `url.path`, and `http.query` span attributes behind `send_default_pii`, consistent with how `client.address` is already handled. These attributes can contain user-provided query parameters and path segments that may include PII, so they should not be captured by default. Fixes PY-2552 Fixes getsentry#6653
…etsentry#6664) Gates `url.full`, `url.path`, and `url.query` span attributes in the Tornado integration behind `send_default_pii`, consistent with the same fix applied to the aiohttp (getsentry#6650) and wsgi (getsentry#6654) integrations. Adds a `send_pii` parametrize dimension to the transactions test to cover both the PII-on and PII-off paths explicitly. Fixes PY-2556 Fixes getsentry#6661 Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
| Back | FazBrowse Home | New Git URL |
The WSGI integration now gates url.full, url.path, and http.query span attributes behind send_default_pii, consistent with how client.address is already handled. These attributes can contain user-provided query parameters and path segments that may include PII, so they should not be captured by default.
Fixes PY-2552
Fixes #6653