Or another question, is there a way to use domain names redirect using
pattern-based rewrite?
Regards,
Tito
On Mon, Dec 17, 2012 at 2:07 PM, Tito Garrido wrote:
> Hi Folks!
>
> I have a bunch of domain using the same application so I have something
> like:
> routers = dict(
> BASE = dict(
Great. Thanks for checking.
On Sunday, November 20, 2011 12:01:41 PM UTC-5, Niphlod wrote:
>
> yes, as far as I can tell the patch solved the infinite loop problem.
> All other things are working correctly: it did not brake anything as
> far as my tests gone.
>
> On 20 Nov, 17:14, Anthony wrote:
yes, as far as I can tell the patch solved the infinite loop problem.
All other things are working correctly: it did not brake anything as
far as my tests gone.
On 20 Nov, 17:14, Anthony wrote:
> OK, so specifically regarding routes_onerror, has the recent patch
> eliminated the infinite loop pro
OK, so specifically regarding routes_onerror, has the recent patch
eliminated the infinite loop problem (and not broken anything else), as far
as you can tell?
And yes, the pattern-based and parameter-based systems cannot be mixed --
you must use one or the other. routes_onerror, however, works
so, here's a few tests on the functionality at the current state
(patch applied). Maybe we can sum up a little "recipe" to explain
better
the "interaction" between parameter based and pattern based
rewrite
These settings for production sites are a real deal, so, here we
are...
The test is a ba
ok, I'll try to mess it up and see what is working and what is not.
Thanks
Niphlod
The patch is now in trunk -- please test. If you can, it would be helpful
if you could try it out with different types of rewrite rules. Also, try it
using the parameter-based rewrite system, as well as with no rewrite rules
at all (want to make sure we didn't break anything).
FYI, an easier wa
See https://groups.google.com/d/topic/web2py-developers/JsY5uO02664/discussion.
On Friday, November 18, 2011 2:20:24 PM UTC-5, Niphlod wrote:
>
> feel free to suggest anything you want, I'm happy to test it
> heavily :D
>
> On 18 Nov, 18:50, Anthony wrote:
> > Looks like this is a bug. I may h
feel free to suggest anything you want, I'm happy to test it
heavily :D
On 18 Nov, 18:50, Anthony wrote:
> Looks like this is a bug. I may have a fix...
>
> Anthony
>
>
>
>
>
>
>
> On Friday, November 18, 2011 9:31:00 AM UTC-5, Niphlod wrote:
>
> > Hi Anthony, /errors/index function is a simple:
Looks like this is a bug. I may have a fix...
Anthony
On Friday, November 18, 2011 9:31:00 AM UTC-5, Niphlod wrote:
>
> Hi Anthony, /errors/index function is a simple:
>
> def index():
> #response.status = request.vars.code
> return dict(vars=request.vars)
>
> Notice the response.stat
Hi Anthony, /errors/index function is a simple:
def index():
#response.status = request.vars.code
return dict(vars=request.vars)
Notice the response.status line commented, it's the one triggering the
loop.
The template is very simple, in fact I simulated all kinds of error
and it gets ren
What does your /errors/index function look like? Also, is that your exact
routes_onerror? I ask because there is a bug (now fixed in trunk) that
leads to a loop if your routes_onerror path is missing the leading '/'
(i.e., 'errors/index' would create a loop, whereas '/errors/index' would
not).
12 matches
Mail list logo
