On Jan 23, 8:55 pm, mdipierro <[email protected]> wrote: > It is a bit clunky to configure because you have to use routes. You > can have multiple controllers to proxy different servers. Similarly to > the original Django code it does not carry forward headers from the > request. This means range requests, if modified since, streaming, does > not work. It is a bit slow.
Well, thanks anyway :) Seems like this doesn't really do what we wanted anyway...this allows us to proxy requests via a proxy server. What we wanted was an actual proxy server. I must have read the Django app's docs wrong! Luckily we have a working port of the CGI version...currently very basic, but we can build on it :) Many thanks, Fran. -- You received this message because you are subscribed to the Google Groups "web2py-users" 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/web2py?hl=en.
