[wildfly-dev] Has Undertow changed the way it processes Link headers

[Michael Musgrove]

I should have mentioned that we are using the format defined in Web 
Linking RFC 5988 (https://datatracker.ietf.org/doc/rfc5988/), which is 
at draft status, to construct our Link headers. For example:

curl -X POST --header "Link: 
<http://127.0.0.1:8888/xid/131077%3a100%3a0%3a1%3a1379280076%3a834173/terminate>;rel="terminator",<http://127.0.0.1:8888/xid/131077%3a100%3a0%3a1%3a1379280076%3a834173/status>;rel="participant"" 
http://localhost:8080/rest-tx/tx/transaction-manager/0_ffffac118314_-2cc33a11_523636ae_342


> The BlackTie (an XATMI implementation) software uses the REST interface
> to JBoss transactions and sends HTTP requests down a plain C socket.
> Around about the time undertow was upgraded to Beta13
> (https://github.com/wildfly/wildfly/commit/8feb7d7d86e2a9619dbf7997b22d163684e5bf03
> - just over a week ago) the Link header is no longer being passed to our
> Resteasy transaction coordinator (the header is coming through as null).
> I was wondering if anyone is aware of a recent change that may have
> caused this change.
>
> I get the same behaviour if I use cURL to send the header.
>
> Note that it works fine if I send Link headers using
> java.net.HttpURLConnection.
>
> Mike
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev