Missing Error Handling in `set_headers` and `set_headers_async`

[nitish-yaddala]

The set_headers and set_headers_async methods currently assume that response.set_header or response.headers assignment always succeeds.

In practice, especially when supporting multiple frameworks (e.g., FastAPI, Flask, Django), setting headers may:

• Fail silently,
• Raise unexpected exceptions (e.g., TypeError, ValueError),
• Encounter immutable response objects.

Affected Code

• set_header(header_name, header_value) — Line 247, Line 275, Line 278
• response.headers[header_name] = header_value — Line 251, Line 282

Recommendation

• Wrap all set_header calls inside try-except blocks.
• Capture at minimum:
  • TypeError
  • ValueError
  • Any web framework-specific exceptions (e.g., attribute errors for immutable headers).
• Log the error or raise a custom error with a meaningful message.
• Ensure header application failures are either safely skipped or fail-fast based on the criticality.