It's okay; I'm used to every now and then opening port 80 in the
firewall when working with Apache (web server).
I guess then, there's something wrong with the GAE dev env. because I
never had that connection problem with Apache regardless of how I
access it and from what browser.
On Jan 23, 9:38
Glad that helped.
When you run the server without an (--address) argument it only
listens on localhost (127.0.0.1) and is not accessible by other
computers but when you specify an address the server becomes
accessible to other computers over the network and your firewall
detects that and prompts y
Yep, that does it. Weird!
When I tried to start the application I got a message from Windows
Firewall and I had to "allow" access to pythonw.exe...I never got that
message before, so I guess the --address=0.0.0.0 triggers it.
Thanks a lot.
On Jan 23, 7:30 pm, Bryce Cutt wrote:
> I have run into t
I have run into this issue before.
The dev server only handles one request at a time. This problem could
have something to do with the browser making multiple requests to the
server at the same time (like Chrome often does) or it could be that
you used a different browser to connect to the server
