Hi,
>
> apr_os_thread_t os_thd = apr_os_thread_current ();
> apr_thread_t *apr_thd;
> apr_status_t apr_os_thread_put(&apr_thd, &os_thd, r->pool);
>
Okay, this clearly doesn't work. I misunderstood the documentation,
but the sources don't lie. Anyway, how can I get the apr_thread_t for
the curren
Hi,
Is there a way to let a MPM worker thread exit after serving X requests? I
need to do some tests that requires checking if my custom hook
ap_hook_thread_exit() is called properly. I found a directive to have one
thread per child that gets me in the right direction (ThreadsPerChild 1).
Now I ne
I posted this on the users list, but didn't get any help, so I'm hoping
the dev people here can either help or at least explain if what I'm
seeing below is how it's meant to work..
I have a uri with cachebusting in it that looks like this:
/path?killCache=x¶meter1=y%parameter2=z
where x is a unix
If you're doing your rewrite in .htaccess,
it _MAY_ help to move that rewrite to httpd.conf.
In many cases rewrite rules in httpd.conf get
processed at an earlier stage than those in
.htaccess. This is becase Apace can't read
the .htacces file until after it resolves the
URL into a filenam
Sounds like a badly broken application to me. If the data is truly
cacheable, the application shouldn't be taking explicit steps to try to
prevent just that. Depending on what the backend system is, you might
be better off using some kind of a filter to just remove that killCache
parameter in the
