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
Right now, header data is stored internally using a regular Map. Right now, if you are consuming a ProtocolEvent and would like to get header data, you do something like this:
However if the header is stored internally as X-Forwarded-For or some other casing, the above returns null despite the header being present. We should consider switching to using a TreeMap or similar implementation which can use case-insensitive keys, because header keys are case-insensitive.
The text was updated successfully, but these errors were encountered:
Right now, header data is stored internally using a regular Map. Right now, if you are consuming a
ProtocolEvent
and would like to get header data, you do something like this:However if the header is stored internally as
X-Forwarded-For
or some other casing, the above returnsnull
despite the header being present. We should consider switching to using a TreeMap or similar implementation which can use case-insensitive keys, because header keys are case-insensitive.The text was updated successfully, but these errors were encountered: