<div dir="ltr">There is not really any way to do this at the moment. The order should not matter for HTTP headers, so we don't provide any way to access this.<div><br></div><div>If you want to do this I think you will have to maintain a custom fork.</div><div><br></div><div>Stuart</div></div><br><div class="gmail_quote"><div dir="ltr">On Fri, Aug 24, 2018 at 6:49 PM Ilpo Ruotsalainen <<a href="mailto:ilpo.ruotsalainen@oath.com">ilpo.ruotsalainen@oath.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi,<div><br></div><div>A project we're working on has recently ran into a need to access the HTTP request headers in order they were received. This does not seem currently possible as HeaderMap is just a hash table.</div><div><br></div><div>One way I see to get this functionality would be to make HeaderMap non-final and provide a mechanism for configuring the class used for request headers, but I don't particularly like this as the HeaderMap API is fairly wide and some of the methods are semantically tricky for this particular purpose.</div><div><br></div><div>Obviously we'd prefer a solution where the modifications to Undertow itself are acceptable for upstreaming so we don't have to maintain a custom fork of it. Any suggestions would be appreciated.</div></div>
_______________________________________________<br>
undertow-dev mailing list<br>
<a href="mailto:undertow-dev@lists.jboss.org" target="_blank">undertow-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/undertow-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/undertow-dev</a></blockquote></div>