FYI, I've added an 'http.autoredirect' property that can used to enable
an auto-redirect if really needed by passing it directly to 2.0
Configurable (Client, WebTarget).
Sergey
On 25/06/15 22:09, Sergey Beryozkin wrote:
Thanks for the analysis so far. It does not really bring us any closer
to
I just saw the comment from Daniel Kulp on CXF-6475. Great find, thanks! I'll
comment further on the JIRA ticket.
On Thursday, June 25, 2015 5:41 PM, LBC wrote:
I modified the code to reveal the URIs and updated CXF-6475 with a comment.
The built URIs from CXF and Jersey appear
I modified the code to reveal the URIs and updated CXF-6475 with a comment.
The built URIs from CXF and Jersey appear to be identical.
Unfortunately, I don't have the cycles w/ work to dig into it further than
that, but I'll Brian Risk from Quandl support (the WS provider) to comment on
what co
Thanks for the analysis so far. It does not really bring us any closer
to finding where the problem is.
Try the following:
1. Compare URIs created by CXF and Jersey. There has to be some
difference, possibly a subtle one somewhere.
2. Check if CXF sends multiple requests - may be the target s
I've attached the tcpdump files to the ticket:
https://issues.apache.org/jira/browse/CXF-6475
BTW, I don't have access to the server side as I'm the WS consumer. I do have
a support agreement with the WS provider though so if necessary I can possibly
request logs from them. However, it would s
Sorry, I didn't realize the formatting would get messed up like that. I forgot
to mention that the 301 and 200 responses I was seeing, I confirmed also
through curl and wget. I've included these outputs in the ticket
(https://issues.apache.org/jira/browse/CXF-6475). I'll work on grabbing the
Hi
You could've just posted a link to CXF-6475 to make it easier to read
this message.
I do not see where the issue is. HttpConduit logging is a bit confusing
indeed because there's a number of attempts to set TLS client parameters
but it does not mean that HTTPS is not used.
Can you trace t
hi,
I'm having problems establishing a secure connection using CXF/JVM defaults.
Hopefully it's just a simple configuration issue. Below is the generic JAX-RS
2.0 code, along with the associated Maven dependency, and the log output
demonstrating the problem. Even though I'm specifying a "https
