Please also note my setup:
https:nginx (load balancer with ssl) - http:nginx - uwsgi
--
---
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
Hi,
Thanks for your reply.
But still this problem will exist as
{{=URL(f='temp.json', hmac_key=, user_signature=True)}} will
output something like below :
'/init/default/temp.json?_signature=88c1fcf27e16dc114ba7f9ce7700fa4ae7ed7267'
$c = 'init'
$f = 'default'
Therefore
This was a tricky one. The $f does not match the extension.
routes_in = (
( '/$c/$f' , '/init/$c/$f' ),
( '/$c/$f\.$e' , '/init/$c/$f\.$e' ),
( '/$c/$f/$anything' , '/init/$c/$f/$anything' )
)
routes_out = (
( ''/init/$c/$f' , '/$c/$f' ),
( ''/init/$c/$f\.$e' , '/$c/$f.$e' ),
Hi,
I am trying to make the home page of the
http://111.111.111.11:8000/welcome/default/indexhttp://130.179.130.86:8000/welcome/default/index
which is the default page loaded when I type
http://111.111.111.11:8000http://130.179.130.86:8000/welcome/default/index,
to
web2py does not use a file called router.py. All rewrite code goes in
routes.py. You can use either the parameter-based system (router.example.py
is an example) *or* the pattern-based system (routes.example.py is an
example), but not both.
Anthony
On Wednesday, July 11, 2012 4:49:33 PM UTC-4,
Note, when you create or change routes.py, you need to reload it before it
will take effect (either restart the server or click the Reload routes
button in the admin interface).
Anthony
On Wednesday, July 11, 2012 5:14:20 PM UTC-4, Anthony wrote:
web2py does not use a file called router.py.
but /myapp/somefunction does not map to /myapp/default/somefunction because
somefunction is interpreted as a controller in that URL (instead, it maps
to /myapp/somefunction/index, and you get an error because such a
controller doesn't exist).
so what does one do if one wants
OK, so you want /myapp/args to be mapped to
/myapp/default_controller/default_function/args. By default args would be
interpreted as a function name and will be mapped to
/myapp/default_controller/args. To change that you need to define a list of
functions for the default controller. Then if
Thank you for the clarification, I understand it better now. I was indeed
confused by the statement you quoted, I had thought that web2py's base
behavior would that if it couldn't find a controller corresponding to
somefunction, it would then invoke the default controller and search for
Sorry if I wasn't clear, I actually meant URLs of the following form,
myapp/controller/args to be mapped to myapp/controller/index/args. The
second point of confusion takes a different tack on web2py routing than the
first point.
I'll try to experiment with your solution though.
For future
Sorry I posted too early,
My solution is:
in routes.py in the base folder, where myapp is the actual name of the
application I'm developing.
routes_app = ((r'/(?Pappwelcome|admin|myapp)\b.*', r'\gapp'),)
and in myapp's folder, I have another routes.py with the following,
routes_in =
I believe to hide 'default' and 'index' you need to use routes.py and:
routers = dict(
# base router
BASE = dict(
default_application = 'init',
default_controller = 'default',
default_function = 'index',
),
)
Setting the default application will hide it as
Oh, I see, that's how you code the REST stuff. My bad.
The web2py book and documentation has led me to believe that the following
would work;
http://120.0.0.1/myapp/default/somefunction can be written as
http://120.0.0.1/myapp/somefunction but I get invalid request error
Here's what the book says:
web2py maps a URL of the form:
1.
14 matches
Mail list logo
