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 pm, Bryce Cutt <[email protected]> wrote: > 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 you. Keep in mind that if you tell your > firewall to allow all traffic to the dev server then other users on > your network could access it (whether this is good or bad depends on > who is on your network). > > On Jan 23, 7:19 pm, MdeA <[email protected]> wrote: > > > > > > > > > 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 <[email protected]> wrote: > > > > 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 and that browser > > > has created a persistent connection. > > > > I found that if I use the argument "--address=0.0.0.0" when starting > > > the dev server (so that it listens on all addresses) and then I access > > > the dev server by the computers actual IP address (instead of using > > > localhost or 127.0.0.1) you don't run into this issue. YMMV. > > > > On Jan 23, 6:06 pm, MdeA <[email protected]> wrote: > > > > > I just got a new PC with Win7 64-bit and IE9. > > > > Now when I request some pages in IE9 from my dev environment it hangs > > > > and while that happens all the other browsers are not able to request > > > > any page from the application until I stop it and start it again. > > > > > It is only in the dev environment because once deployed IE9 can load > > > > all pages from the live website without any issues, but I'd like to be > > > > able to see how my app works with IE before I deploy it. > > > > > Any ideas? > > > > Thanks. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
