This would have been in the parent process in the monitor hook or used in
the child init hook. The ability to use it in either would be good. I
think the easiest approach for me would be to use libCurl or an equivalent
simple client side lib. I'm not sure how to properly populate a
request_rec*
On May 6, 2010, at 4:22 PM, Some Guy wrote:
> What we want to do is create the subrequest (or maybe just a request)
> without any previous request_rec* object. At least that is what I figured
> markus meant when he said "build a request completely free". From the APIs,
> this does not seem possi
What we want to do is create the subrequest (or maybe just a request)
without any previous request_rec* object. At least that is what I figured
markus meant when he said "build a request completely free". From the APIs,
this does not seem possible, and using libCurl may be the better solution.
O
On May 6, 2010, at 8:40 AM, Some Guy wrote:
> I wanted to do something similar, but the Apache 2 APIs require a
> request_rec* in the lookup_uri method. Tracing the code in request.c, it
> uses the passed in request_rec* in make_sub_request.
>
> The example Joe provided won't compile, and the re
I wanted to do something similar, but the Apache 2 APIs require a
request_rec* in the lookup_uri method. Tracing the code in request.c, it
uses the passed in request_rec* in make_sub_request.
The example Joe provided won't compile, and the request_rec can't be NULL
otherwise the code will segfaul
((template_context *)f->ctx)->include_r =
ap_sub_req_lookup_uri(uri,f->r,((template_context *)f->ctx)->include_filter);
apr_table_setn(((template_context
*)f->ctx)->include_r->notes,TEMPLATE_OVERRIDE_PARSER,"-");
if template_context *)f->ctx)->include_r != NULL) && (((template_context
*)