t; >>> the cluster we use plain HTTP for speed.
> >>>
> >>> Now, CXF has a habit of rewriting my carefully crafted endpoint URLs
> >>> in my WSDL, thus reporting plain HTTP endpoints on the services/ page
> >>> and in the final WSDL, when
nd in the final WSDL, when in fact they should be HTTPS.
Is there a way configure this behavior?
--
Venlig hilsen / Kind regards,
Christian Vest Hansen.
--
View this message in context:
http://www.nabble.com/endpoint-rewriting-tf4717550.html#a13488677
Sent from the cxf-user mailing list archive at Nabble.com.
vior?
> >
> >
> > --
> > Venlig hilsen / Kind regards,
> > Christian Vest Hansen.
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/endpoint-rewriting-tf4717550.html#a13488677
> Sent from the cxf-user mailing list archive at Nabble.com.
>
>
--
Venlig hilsen / Kind regards,
Christian Vest Hansen.
SDL, when in fact they should be HTTPS.
>
> Is there a way configure this behavior?
>
>
> --
> Venlig hilsen / Kind regards,
> Christian Vest Hansen.
>
>
--
View this message in context:
http://www.nabble.com/endpoint-rewriting-tf4717550.html#a13488677
Sent from the cxf-user mailing list archive at Nabble.com.
I deploy a CXF web service to a cluster that sits behind a content switch.
We have HTTPS on the content switch for security, but internally in
the cluster we use plain HTTP for speed.
Now, CXF has a habit of rewriting my carefully crafted endpoint URLs
in my WSDL, thus reporting plain HTTP endpoi
