Summary:

Investigate how Eventlet handles UTF-8 in HTTP response headers, assess risks of changing current `latin-1` encoding, and explore alternatives or documentation as a known issue.

Goal:

• Determine whether UTF-8 header values are permitted by HTTP specifications (especially HTTP/2).
• Assess the impact and risk of changing Eventlet’s hardcoded `latin-1` encoding.
• Decide between: fixing the issue, applying a workaround (e.g., percent-encoding), or documenting it as a known limitation.

TimeBox:

2 days

Deliverables/Outcomes:

• A comment summarizing findings on spec compliance and encoding expectations.
• Risk analysis of modifying header encoding in Eventlet (e.g., backward compatibility, regression potential).
• Clear recommendation: fix, workaround, or known issue.
• If fix or workaround is chosen: create Stories for implementation and testing.