The only question is: how do you want that to look?
All web2py interfaces currently only take one IP and socket number. I
don't think it's wise to assume that if someone wants HTTPS they
automatically want HTTP as well (and pick the port for them). You
decide how you want the Tk frontend,
true and there are security advantages to have two processes serve 80
and 443 respectively. Let's think about this some more.
On May 14, 7:52 am, Timothy Farrell tfarr...@swgen.com wrote:
The only question is: how do you want that to look?
All web2py interfaces currently only take one IP and
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.
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
On 5/13/2010 1:40 PM, Miguel Lopes wrote:
On Wed, May 12, 2010 at 7:45 PM, Timothy Farrell
Since rocket does it, is there any way we can add support for 80+443
with one rocket and one web2py instance?
On May 13, 3: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
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
6 matches
Mail list logo
