On Sat, 5 Oct 2013 05:05:26 -0700 (PDT) Niphlod <[email protected]> wrote:
> then let's make things even easier .... web2py expects a > parameters_xxx.py file that is extracted from > request.env.server_port OK, now it's even more clear. > make a test page that does > > def test(): > return dict(a=request.env.server_port) > > and see where web2py is told to listen on :D Obviously, if web2py refuses to work without parameters_80.py is that it is listening on port 80. What is not clear and is puzzle to me is where in the setup it is told so? When I try with the above test page, Firebug shows w.x.y.z:443 as IP, gunicorn is also listening on port /= 80...can you help with it? > BTW, I didn't mean that you **need** to look over at all the source > code of web2py on the first day, but that's pretty much the beauty of > opensource ... you **can** read it :P Yeah, I'll do it, but on the 7th day. ;) Sincerely, Gour -- Whenever and wherever there is a decline in religious practice, O descendant of Bharata, and a predominant rise of irreligion — at that time I descend Myself. http://www.atmarama.net | Hlapicina (Croatia) | GPG: 52B5C810 -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
