Disabling an app does not affect local requests. Using the hosts file, you
access the app as if it is an external request (via the host name defined
in the hosts file), so disabling is enforced. When you instead switch to
accessing the app locally (i.e., via "localhost" or 127.0.0.1), the
"disabled" file is ignored and access is allowed.
Anthony
On Friday, January 4, 2019 at 12:06:45 PM UTC-5, Shawn Michaels wrote:
>
> Hi,
>
> I just noticed, I can access disabled app.
>
> when I connect from local network with /etc/hosts file edited like this:
> [server IP] [disabled.address]
>
> The page:
> Temporarily down for maintenance
> is displayed
>
> When I comment the hosts line out I can connect to disabled site.
> Do anybody know why or is it something known?
>
> I have defined base router for the disabled and second non-disabled app:
> # -*- coding: utf-8 -*-
>
> routers = dict(
>
> # base router
> BASE=dict(
> default_application='app',
> domains = {
> "[address]" : "app",
> "[disabled.address]" : "disabled_app",
> },
> ),
> )
>
--
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 web2py+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
