...
More information about setting up Weave when it’s behind a reverse proxy can be found here.
HTTPS
Most likely the Weave instance needs to be accessed securely via HTTPS, not HTTP. However this is yet to be verified thus will be confirmed by Cohga at a later dateIt is likely that the SAML Identity Provider you’re trying to integrate with Weave will require that the callback request it makes to the Weave server be made using a secure connection, meaning that the Weave server will have to be configured, and accessed by the user, via HTTPS rather than plain HTTP.
Acegi, Spring Security, Container and SAML
...