Issue 7253043: Serve HTTPS and WebSocket on the same port.
DescriptionServe HTTPS and WebSocket on the same port.
The WebSocket connection must be established on
port 443, so that using Firefox securely no longer
requires the user to accept a self-signed certificate
twice: once for the HTTPS port and once for the wss port.
HAProxy is used to do that: juju-gui/ppa contains the
development release of HAProxy, supporting SSL.
HTTPS traffic is sent to nginx (port 8000), and wss
connections are redirected to the underlaying API
backend (port 8080). The juju-api-port option has been
removed: since that port is no longer exposed, the one
being used can be considered just an internal
implementation.
Other changes:
Updated documentation.
Moved static upstart configuration files set up to the
install hook. This way, a config change no longer causes
them to be rewritten as they are over and over.
Some renaming and clean up.
QA:
- deploy the charm
- open the application using Firefox
- add the security exception
- you should see the Juju GUI login screen
- now try staging: juju set juju-gui staging=true
- compulsively refresh Firefox
- admire the services
https://code.launchpad.net/~frankban/charms/precise/juju-gui/bug-1104098-same-port/+merge/145940
(do not edit description out of merge proposal)
Patch Set 1 #
Total comments: 9
Patch Set 2 : Serve HTTPS and WebSocket on the same port. #
Total comments: 8
Patch Set 3 : Serve HTTPS and WebSocket on the same port. #Patch Set 4 : Serve HTTPS and WebSocket on the same port. #
MessagesTotal messages: 7
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
