11:10 a.m.
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/8feb7d7d86e2a9619dbf7997b22d163...
- 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
11:16 a.m.
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/term...
http://localhost:8080/rest-tx/tx/transaction-manager/0_ffffac118314_-2cc3...
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/8feb7d7d86e2a9619dbf7997b22d163...
- 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(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev
11:25 a.m.
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/3758226082a90de5a129024de9a2215...
it might have to do also with that.
--
tomaz
On Wed, Sep 25, 2013 at 6:10 PM, Michael Musgrove <mmusgrov(a)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/8feb7d7d86e2a9619dbf7997b22d163...
- 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(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev
4075
days inactive
4075
days old
2 comments
2 participants
participants (2)
-
Michael Musgrove -
Tomaž Cerar