You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During #1778, I've been reminded that HTTP permits both requests and responses to have duplicated headers—that is, to have multiple values for the same key. We should make that securedrop-proxy supports these cases at least as well as suggested by VCR.py's HeaderDict.
The text was updated successfully, but these errors were encountered:
On Mon, Feb 05, 2024 at 12:09:53PM -0800, Kunal Mehta wrote:
For prioritization purposes, is there any place we currently use or
expect duplicate headers?
Nope! Just seemed worth noting this as a compliant thing we don't
currently support.
Description
During #1778, I've been reminded that HTTP permits both requests and responses to have duplicated headers—that is, to have multiple values for the same key. We should make that
securedrop-proxy
supports these cases at least as well as suggested by VCR.py'sHeaderDict
.The text was updated successfully, but these errors were encountered: