On Tuesday, April 8, 2014 9:51:55 AM UTC-7, peter wrote: > > I have a web2py driven website. > > http://162.218.210.94/new_spin2/default/events > > works every time. > > However the routed version > > spinjazz.net/events which points to the same page works 80% of the time, > 20% of the time it gets. > > invalid request. > > Now I think that this might just be true because of conditions currently > in operation about speed of operation. eg it did not seem true yesterday, > but is consistently true at the moment. > > So are there timing issues that can cause routing to go wrong? Is there > anything I can do to avoid getting the 'invalid request message'? > > Thanks > > Peter > > > Well, doesn't the answer depend on how you're interfacing Web2Py to the internet? Are you using the stock Rocket server, or Apache+wsgi, or nginx, or .... ?
If Apache, the gurus might also want to know how many threads you're setting up, etc. /dps -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
