I'm having this strange problem, and I would like to know if it is a web2py 
bug or is something that I'm missing.

My web2py app is accesed through a domain, and in the model file, I connect 
to the db and to the session like this:

db = DAL('postgres:.....', migrate=False, lazy_tables=True)
session.connect(request, response, db=db, masterapp='myapp')

It's a bit difficult to explain the problem, so here are the steps to 
reproduce it:

   1. *From a mobile device using Chrome or Firefox*, open this website 
   http://nachoesbo.com (this will ejecute the /default/index).

   2. Browse the web nachoesbo.com for a few seconds.
   
   3. Try to access the same web through Chrome or Firefox *in a desktop pc 
   using **the same internet connection*. 
   In this point, the browser will stay "connecting" to domain, and it will 
   hang until timeout. 
   This situation will stay this way until you close the mobile browser (or 
   after a few minutes).
   
   
I'm really pulling my hair off with this. 
I'm experiencing the same problem with all of my web2py applications.
The same problem occurs using a different router and a different ISP.

I've checked the cookies and there is nothing odd. I don't store anything 
in the cookie, it's just the default behaviour. 

What could I be missing?



-- 
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.

Reply via email to