Thanks of your help.
I just fix it. :) what ever, I just don't want every one can visit
database by such well-known URL "_ah/admin". So I change it.
On Aug 25, 12:13 am, "Nick Johnson (Google)"
wrote:
> Hi Allen,
>
> On Mon, Aug 24, 2009 at 4:37 PM, Allen wrote:
>
> > Hi Johnson,
>
> > I run t
Hi Allen,
On Mon, Aug 24, 2009 at 4:37 PM, Allen wrote:
>
> Hi Johnson,
>
> I run the application in my local LAN. for example:
>
> dev_appserver.py -a 192.168.1.1 -p 80 myapp
>
> then every one under 192.168.1.x can visit this app by http://192.168.1.1/
> but they can also visit the database di
Hi Johnson,
I run the application in my local LAN. for example:
dev_appserver.py -a 192.168.1.1 -p 80 myapp
then every one under 192.168.1.x can visit this app by http://192.168.1.1/
but they can also visit the database directly by http://192.168.1.1/_ah/admin
How can I make sure the "_ah/admin
Sounds like you want to show one URL to your admin/users when on dev,
and another URL when on live/production server?
If so, see this post for Python solution:
http://groups.google.com/group/google-appengine-python/browse_thread/thread/d1537b3ea289322e#
Neal
--~--~-~--~~~
Hi Allen,
On Mon, Aug 24, 2009 at 2:36 AM, Allen wrote:
>
> As we know we can use "http://localhost/_ah/admin"; to go through the
> local database before upload to GAE. And we can not directly use
> "http://www.mydomain.com/_ah/admin"; to visit the online database after
> "appcfg.py" to GAE.
>
