On 3 Oct 2013, at 5:36 AM, Anthony <[email protected]> wrote:
> On Thursday, October 3, 2013 12:36:34 AM UTC-4, Jonathan Lundell wrote:
> On 2 Oct 2013, at 10:36 PM, Anthony <[email protected]> wrote:
>> A couple years ago, Jonathan seemed to think this behavior was a bug and
>> alluded to a fix in trunk:
>> https://groups.google.com/d/msg/web2py/elnV_6Ntw3E/KWNlpoJfpWAJ.
>
> See if setting exclusive_domain=True in the router helps.
>
> From that earlier discussion, it sounded like this was supposed to be the
> behavior even without setting exclusive_domain to True. Was the old behavior
> kept for backward compatibility?
>
The relevant line (MapUrlIn.map_app):
if not base.exclusive_domain and base.applications and arg0 in
base.applications:
This is the highest-priority test for resolving the app identity; arg0 is the
(current) leftmost item of the incoming path. The following test is relevant as
well; the third & fourth handle domain mapping.
And *then* we repeat the first two tests but without exclusive_domain. That may
have been the
Per the old thread, it might be best to make exclusive_domain default to True.
In the thread, I mention removing the option and forcing it always; at the
moment I can't think of a case where it'd be desirable for it to be False, but
my imagination might simply be not up to the task.
--
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.
