rave-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marlon Pierce <marpi...@iu.edu>
Subject Re: Rave+HTTPS only on Port 443?
Date Mon, 10 Sep 2012 19:43:32 GMT
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

We could get to the login page OK if using 8443, but then suffered
meltdown when logging in. We'll dig up the stacktrace.


Marlon


On 9/10/12 3:35 PM, Jasha Joachimsthal wrote:
> Couldn't you access the portal at all or were you able to log in,
> but none of the widgets rendered?
> 
> Jasha
> 
> On 10 September 2012 20:10, Marlon Pierce <marpierc@iu.edu> wrote:
> 
> 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/

iQEcBAEBAgAGBQJQTkLkAAoJEOEgD2XReDo5NSYH/2+wCIssx9X9Pp19tJTXJTZF
/+pxK3iIlhF+/7nZ5mWmt3evtwhzR88ETYiZXciwYxmkhqZqcInM6ZrOuAaEYrh1
ThFNOVIJkHvg5XLBTp0tN7d0OWSGNfRaQpzhCXJse0CbLTOCo4KqMd301E3goCqE
SQ3ryhPwHlbLslMDu+PF+dnzJvdF+/BlKbTm/RG/55ECA/ioVN5DkAv9Qd/k3Kzk
c3GXwGJgBioBldXWdG1+lj9HAzgtsIDTIt0GkqR1GR7Y/TPp3n67VSQ2D1qd9Nfm
3Sa6FPRx0rSdmafp69mXZItPuWty2kb9/YN46GZysYMC0/keHw4yzYQFLv5Qow0=
=cWwn
-----END PGP SIGNATURE-----

Mime
View raw message