On Fri, Oct 25, 2013 at 10:10 AM, Yann Ylavic <ylavic....@gmail.com> wrote: > How about setting backend->r to r->backend (when applyable)? > > For now backend->r is pooled to backend's connection, and has a different > lifetime than r but maybe it worth having it destroyed with r (setting > things related to the origin's connection to NULL, when released, to avoid > invalid accesses)... > > Hence r->backend->useragent_addr/useragent_ip (useragent is the origin here) > are accessible everywhere, and so are backend->r->headers_* and everything > related to the request/response send/received to/from the backend. > > I may be missing lot of things with backend->r's lifetime, since it is now > attached to origin->pool, surely for good reasons... > Also, not all proxy modules use backend->r, but maybe these can create a > fake request too with everything NULL except sockaddr (and other relevant > things, if any).
I think the how simple the data is compared to that underlying structure, I would rather see it in a flat table that other proxy-like things could emulate. Similar to SSL variables.
