Re: Is there are any way to know if the request is regular (http) or SSL (https) in a module?

2007-12-17 Thread Graham Dumpleton
On 18/12/2007, Sander Temme <[EMAIL PROTECTED]> wrote: > > On Dec 17, 2007, at 6:36 PM, Eric Covener wrote: > > >> I would like to know the request type in my module > >> (handler/filter), is there any way to know that (HTTP > >> vs HTTPS)? > > > > apr_table_get(r->subprocess_env, "HTTPS") might b

Re: Is there are any way to know if the request is regular (http) or SSL (https) in a module?

2007-12-17 Thread Sander Temme
On Dec 17, 2007, at 6:36 PM, Eric Covener wrote: I would like to know the request type in my module (handler/filter), is there any way to know that (HTTP vs HTTPS)? apr_table_get(r->subprocess_env, "HTTPS") might be what you want That gets set in the Fixup hook, relatively late in the req

Re: Is there are any way to know if the request is regular (http) or SSL (https) in a module?

2007-12-17 Thread Eric Covener
On Dec 17, 2007 9:23 PM, John Zhang <[EMAIL PROTECTED]> wrote: > I would like to know the request type in my module > (handler/filter), is there any way to know that (HTTP > vs HTTPS)? apr_table_get(r->subprocess_env, "HTTPS") might be what you want -- Eric Covener [EMAIL PROTECTED]

Is there are any way to know if the request is regular (http) or SSL (https) in a module?

2007-12-17 Thread John Zhang
I would like to know the request type in my module (handler/filter), is there any way to know that (HTTP vs HTTPS)? Thanks, John

Re: Memory issue in apache modules

2007-12-17 Thread John Zhang
--- Joe Lewis <[EMAIL PROTECTED]> wrote: > Your buckets can still be created using the > request->pool . My created > buckets in my output filter are done that way. Have > you tried it? You > still use the request->connection->bucket_alloc for > the other parameter, > but the request->pool for

Re: Memory issue in apache modules

2007-12-17 Thread Joe Lewis
John Zhang wrote: > --- Ray Morris <[EMAIL PROTECTED]> wrote: > > >>> I am using the apr_* functions to allocate >>> memory (most of the time from the request->pool). >>> >>If there are few places where you allocate from >> othr than the reqquest pool, I'd look at those >> first. >>