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

[Tomaž Cerar]

Hi,

there should be noting directly related to processing headers
see commit history of undertow
https://github.com/undertow-io/undertow/commits/master

What I don't get in your questions is that it works when you are doing
client request via HTTPUrlConnection it works, otherwise it doesn't?
That sounds extra fishy.

Also there was RestEasy upgrade recently...
https://github.com/wildfly/wildfly/commit/3758226082a90de5a129024de9a22154236427b1
it might have to do also with that.

--
tomaz


On Wed, Sep 25, 2013 at 6:10 PM, Michael Musgrove <mmusgrov at redhat.com>wrote:

> 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/wildfly-dev/attachments/20130925/e87fb23e/attachment.html