krishicks 481ce566e1 fix(ocsf): correct HTTP activity context (#3316) ...

Previously, metadata events omitted both HTTP request and response objects,
early proxy rejections used HTTP Activity without request context, and
unsupported-scheme events did not expose enough safe HTTP context to satisfy
the OCSF 1.8 schema.

Now, metadata events include a method-only request and their actual HTTP
response codes without recording the metadata URL. Unsupported-scheme events
also include a method-only request plus the generated 400 response. Authority
mismatches and credential-resolution denials use HTTP Activity with their
generated 403 or 500 responses, and HTTP activity IDs are derived from the
request method.

Additionally, HttpActivityBuilder now enforces the OCSF request-or-response
constraint at compile time.

Signed-off-by: Kris Hicks <khicks@nvidia.com>

2026-09-15 18:47:55 +00:00

..

accessing-logs.mdx

feat(sandbox): add canonical main process (#2726)

2026-08-20 22:18:23 +00:00

logging.mdx

refactor(inference): remove managed inference routes (#3195)

2026-09-09 18:47:22 +00:00

ocsf-json-export.mdx

fix(ocsf): correct HTTP activity context (#3316)

2026-09-15 18:47:55 +00:00