-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all--
We were reviewing the Rave+SSL instructions (http://rave.apache.org/documentation/configure-ssl.html) and noticed it requires using port 443. The instructions worked as written (and didn't if we used 8443). Does anyone know the source of this constraint? It would be much better for development purposes to not require restricted ports. Also, has anyone looked at using Apache HTTPD + SSL + proxying as an alternative? Thanks-- Marlon -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.16 (Darwin) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iQEcBAEBAgAGBQJQTi0jAAoJEOEgD2XReDo5P/0H/2D5jHKRKNY+azSRMN8dk8BY RI9JcQmgfiL+RfhFdv2Od8mlJPP7ubeGxXvvjKSfD9nWFWSduVif5r2PTHL6DfD3 iOCh7BJdU6ZiSjRWfADUfUuansLgnpoMxvddiCyoB/LgfZMDQvq0N4OWTJwt3UAp Csr346qGcR2B2ayNHqQgQPz91Ueg77+0Q2xry4bi0DlvsvBncNATk8laXwebFOla 7HsowfmwFZgIqEOj/ezK9q0t2ElK9YXh3YKLxXc/f6Lxpi38LtJzu+DdncElAO8A DrEIJn+Sf7dmUAw7qBWbMLwfQ8rU2IvrfbhMMH0tgGH8p8wwvfnP5QYjE/OKgks= =GMWw -----END PGP SIGNATURE-----
