On Thu, May 13, 2010 at 9:02 PM, Timothy Farrell <tfarr...@swgen.com> wrote:
> While Rocket supports listening on multiple sockets, web2py does not. You > will need to run two separate instances of web2py (one for SSL, one > unencrypted) to do what you are asking. > > -tim > > Txs for the reply. Always nice to know the reason. Keeping with Massimo's suggestion I added solved to the post! LOL > > On 5/13/2010 1:40 PM, Miguel Lopes wrote: > > > > On Wed, May 12, 2010 at 7:45 PM, Timothy Farrell <tfarr...@swgen.com>wrote: > >> This is the error that Jon Lundell's guys found already. Note that it's >> trying to connect to port 8000 as HTTP. Connect as HTTPS and it should >> work. >> >> Also try upgrading to trunk, that should issue a "400 Bad Request". >> >> -tim >> >> Confirmed. > Updated from trunk to 1.77.3 and if attempting to access the server in http > (instead of https) server issues console warning like you said. > > Since I'm on a LAN I installed SSL as a learning experience and to access > the admin interface anywhere on the LAN. However, now that I have web2py > running with SSL, even the applications must be accessed via SSL. I expected > that only the admin would require SSL. Is this also a matter of > configuration or is there some other reason? I do have very little knowledge > on networks and deployment in general. So I wonder what is the reason. > > Miguel > > >
