On Fri, Aug 7, 2015 at 12:46 PM Sergey Beryozkin <[email protected]> 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 headers set when forwarding > Sergey, Thanks for the tip! I'm setting it up in Karaf and have verified that the config is there: config:list "(service.pid=org.apache.cxf.osgi)" ---------------------------------------------------------------- Pid: org.apache.cxf.osgi BundleLocation: mvn:org.apache.cxf/cxf-rt-transports-http/3.0.5 Properties: felix.fileinstall.filename = file:/opt/aetos/etc/org.apache.cxf.osgi.cfg org.apache.cxf.servlet.context = /services org.apache.cxf.servlet.use-x-forwarded-headers = true service.pid = org.apache.cxf.osgi My WADL still has "http" links in it, even though I see these headers when I request the WADL: X-Forwarded-For=[X.X.X.X], X-Forwarded-Port=[443], X-Forwarded-Proto=[https] Can you think of anything I'm missing? Could it be that just the WADL is borked, but usage of UrlInfo in my JAX-RS resources will work fine?
