On Fri, Aug 7, 2015 at 12:46 PM Sergey Beryozkin
wrote:
> CXFServlet has a "use-x-forwarded-headers" boolean parameter, if it is
> set to true then CXFServlet will check X-FORWARDED-PROTO, I recall
> adding the code to support something similar, can you try it, I think
> ELB should have these hea
Okay, found the setting. So, in our systems, can you think of any reason
we wouldn't want our default Karaf setup to have that feature turned on?
Is there a downside to turning it on? Will it break systems which aren't
behind proxies?
On Fri, Aug 7, 2015 at 12:58 PM James Carman
wrote:
> Hrmmm
Hrmmm. We're using CXF inside Karaf. Gotta find where to set that up...
On Fri, Aug 7, 2015 at 12:46 PM Sergey Beryozkin
wrote:
> CXFServlet has a "use-x-forwarded-headers" boolean parameter, if it is
> set to true then CXFServlet will check X-FORWARDED-PROTO, I recall
> adding the code to su
CXFServlet has a "use-x-forwarded-headers" boolean parameter, if it is
set to true then CXFServlet will check X-FORWARDED-PROTO, I recall
adding the code to support something similar, can you try it, I think
ELB should have these headers set when forwarding
let us know if it works
Cheers, Serg
Our CXF services sit behind an ELB which terminates SSL for us, then
forwards the request to our CXF services over HTTP. When we look at the
WADL for the service through the ELB URLs, all of the links in the WADL
have the "http" scheme, not "https". Is there something special we need to
do in ord
Hi Colm,
first of all thanks for help.
I already tested the new functionality and it works fine but during these
tests I have noticed something.
For the testcase you added a new AlgorithmSuite with
"http://www.w3.org/2001/04/xmlenc#rsa-oaep-mgf1p"; in combination with
MGF256, but I think this i
