Il 11/09/14 23:02, Niphlod ha scritto:
> 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.
Hi!
I came to this work in progress solution[1] I'd like to share in order
to fix some open questions.
* First of all I need to proxy even the cookies from the third party app
to the client and back.
I tried something like you can see in the comment out code between the
lines 46 to 58 but without success.
What's the right way to solve it?
* How can I improve parallel calls to get better performances?
* If I pass to the client what the resource-site give me about
content-lenght happens something wrong (and odd).
All requested contents from the page are truncated at the same lenght.
This happens just removing the "content-lenght" from
the tuple at the line 62.
Thanks a lot
Manuele
[1] http://www.web2pyslices.com/slice/show/1993/web2py-controller-as-a-proxy
--
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.
