btw: a session.forget(response) on top of all, if you don't need the sessions to be persisted, may be a good idea to improve parallel calls. on the content-length matter: you should pass what the underlying "resource-site" pass you. The above implementation should be perfectly fine in that respect... if it finds one in the original call, it passes it along untouched.
On Thursday, September 11, 2014 10:48:08 AM UTC+2, Manuele wrote: > > Il 11/09/14 09:12, Manuele Pesenti ha scritto: > > > > I need to proxy an external application but what happens is that the > > first page loading stops at a certain point of the html header, I > > suspect after too mutch requests to the same controller because every > > requirement (like css, js, images and so on) for whom is specified a > > relative path are requested to my proxy controller. Is it possible? > > How can I resolve it? > I answer my self even if not completely... The problem is not the load > but the respose. All requested resources (pages, libraries and so on) > where truncated at the same length. A step behind is performed not > passing the "Content-length" of every resources... > I'll keep you updated. > Cheers > > M. > > > > Thank you > > Cheers > > > > Manuele > > -- 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.
