Re: [web2py] Re: Vanity URLs

Yes, I have the controller with the name view.py and the function user On Wednesday, July 11, 2012 10:14:17 PM UTC+5:30, pbreit wrote: > > I guess this is the key line: > ('/$anything','404->/devekayan/view/user/$anything') > > That would require a controller file called "view.py" and a function "

Re: [web2py] Re: Vanity URLs

Oh... that might be the problem since I am not using the source from the trunk. I am using the current stable version 1.99.7 available at : http://www.web2py.com/examples/default/download On Wednesday, July 11, 2012 10:12:28 PM UTC+5:30, Massimo Di Pierro wrote: > > Are you sure you are sing we

Re: [web2py] Re: Vanity URLs

I guess this is the key line: ('/$anything','404->/devekayan/view/user/$anything') That would require a controller file called "view.py" and a function "def user():"

Re: [web2py] Re: Vanity URLs

Are you sure you are sing web2py trunk? Earlier version do not support the 404-> On Wednesday, 11 July 2012 09:24:03 UTC-5, Sushant Taneja wrote: > > Yes, sure. I have attached my routes.py with this reply. > > On Wednesday, July 11, 2012 7:49:12 PM UTC+5:30, Massimo Di Pierro wrote: >> >> Ca

Re: [web2py] Re: Vanity URLs

Yes, sure. I have attached my routes.py with this reply. On Wednesday, July 11, 2012 7:49:12 PM UTC+5:30, Massimo Di Pierro wrote: > > Can I see your full routes? > > On Wednesday, 11 July 2012 02:26:04 UTC-5, Sushant Taneja wrote: >> >> I wrote the below line in routes.py. But I am getting a serv

Re: [web2py] Re: Vanity URLs

Can I see your full routes? On Wednesday, 11 July 2012 02:26:04 UTC-5, Sushant Taneja wrote: > > I wrote the below line in routes.py. But I am getting a server response of > 400 instead of 404. > > INFO 2012-07-11 07:21:03,242 dev_appserver.py:2952] "GET /staneja > HTTP/1.1" 400 - > > So I t

Re: [web2py] Re: Vanity URLs

I wrote the below line in routes.py. But I am getting a server response of 400 instead of 404. INFO 2012-07-11 07:21:03,242 dev_appserver.py:2952] "GET /staneja HTTP/1.1" 400 - So I tried after changing 404 to 400 but it is still the same. No redirection or request for the target URL is ma

Re: [web2py] Re: Vanity URLs

It can be done already ('/$anything','404->/myapp/default/catchall/$anything') On Saturday, 7 July 2012 18:25:25 UTC-5, pbreit wrote: > > I wonder if we should try to support this formally. Perhaps if as a > "catchall" if the router doesn't find any valid routes and before it > returns a 404?

Re: [web2py] Re: Vanity URLs

On 7 Jul 2012, at 4:25 PM, pbreit wrote: > I wonder if we should try to support this formally. Perhaps if as a > "catchall" if the router doesn't find any valid routes and before it returns > a 404? The parametric router will do this for the default controller and function, if you list the func

Re: [web2py] Re: Vanity URLs

I wonder if we should try to support this formally. Perhaps if as a "catchall" if the router doesn't find any valid routes and before it returns a 404?

Re: [web2py] Re: Vanity URLs

On 7 Jul 2012, at 3:37 PM, Massimo Di Pierro wrote: > The rule you want is > > routes_in = [ > ('/$anything', '/appname/view/user/$anything') > ] > > but before this rule you must make sure treat other URLs as exceptions > (should not be mapped): > > routes_in = [ > ('/admin','/admin'), >

[web2py] Re: Vanity URLs

The rule you want is routes_in = [ ('/$anything', '/appname/view/user/ $anything') ] but before this rule you must make sure treat other URLs as exceptions (should not be mapped): routes_in = [ ('/admin','/admin'), ('/admin/$anythi