Hi all,
When I learn jaxrs spec, I see it said in ApplicationPath doc:
public abstract java.lang.String value
Defines the base URI for all resource URIs. A trailing '/' character will be
automatically appended if one is not present.
The supplied value is automatically percent encoded to conform
Yes. Does the below summary sound ok? Not sure how can I get the
socket reference in the auth supplier, but I haven't really looked too hard.
Once I have it ready, I can do a pull request in github or a patch here
or whatever. What's your preference?
The document http://cxf.apache.org/codi
I've a question about Fediz. I'm currently using to protect a jetty
web application and wondering if it is possible to enable/disable
Fediz authentication dynamically?
For instance I've configured jetty to use a security handler
depicted in code below:
SecurityHandler aSecurityHandler = new Co
Just a quick note that to close a proxy you need to cast to Client first
with a WebClient helper, and then close it...
Cheers, Sergey
On 28/04/15 16:30, Sergey Beryozkin wrote:
Hi Veit
On 28/04/15 16:21, Veit Guna wrote:
Hi Sergery.
On first sight, it seems to work with the HttpClient conduit
Hi Veit
On 28/04/15 16:21, Veit Guna wrote:
Hi Sergery.
On first sight, it seems to work with the HttpClient conduit.
But now I'm wondering, when the created thread-pool of the HttpClient conduit
will be closed.
As I can see, 8 threads are created (=cpu core count) and won't be terminated
on n
Hi Sergery.
On first sight, it seems to work with the HttpClient conduit.
But now I'm wondering, when the created thread-pool of the HttpClient conduit
will be closed.
As I can see, 8 threads are created (=cpu core count) and won't be terminated
on normal
test case exit. So when the client is u
The Fediz subproject of Apache CXF has a new major release - 1.2.0. It has
the following main new features:
- A new REST API for the IdP (1.2)
- Support for logout in both the RP and IdP (1.2)
- Support for logging on to the IdP via Kerberos and TLS client
authentication (1.2)
- A n
If it works with Jersey Client (HttpUrlConnection) and is also known to
work with CXF HttpClient based conduit, then I guess it would narrow it
down to CXF UrlConnectionHttpConduit that might set some of the
properties on HttpUrlConnection which might affect it somehow...
Sergey
On 28/04/15 1
Hi
Thanks for preparing this test, appears to be that using HttpClient
resolves it. So I've updated pom.xml:
org.apache.cxf
cxf-rt-transports-http-hc
3.0.4
test
and added this line to LoadTest(), immediately after creating a proxy,
WebClient.getConfig(myService).getRequestC
Would you be willing to submit a patch for this?
Colm.
On Mon, Apr 27, 2015 at 5:44 PM, David Mansfield wrote:
> Hi All,
>
> Most (*) SPNEGO client implementations will canonicalize a host name when
> using it to create a service principal.
>
> CXF seems to be an exception. If a CNAME is used,
One more option "/post" ?
So is it "post", "../post", or "/post" ?
Sergey
On 28/04/15 10:26, Sergey Beryozkin wrote:
Hi
Thanks for this analysis, I'm looking at the docs, example
https://jax-rs-spec.java.net/nonav/2.0-rev-a/apidocs/javax/ws/rs/core/Response.html#getLink(java.lang.String)
it
Hi
Thanks for this analysis, I'm looking at the docs, example
https://jax-rs-spec.java.net/nonav/2.0-rev-a/apidocs/javax/ws/rs/core/Response.html#getLink(java.lang.String)
it says:
"A relative link is resolved with respect to the actual request URI that
produced this response".
What is the
12 matches
Mail list logo
