Mailing-List: contact users-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@httpd.apache.org
MIME-Version: 1.0
In-Reply-To: <CAJtbAXkkpVV+ExSpoKT3-xvtkVu4hCJV2Wrk1sLt7+LBd7LXtg@mail.gmail.com>
References: <CAJtbAXkkpVV+ExSpoKT3-xvtkVu4hCJV2Wrk1sLt7+LBd7LXtg@mail.gmail.com>
From: Eric Covener <covener@gmail.com>
Date: Thu, 7 Sep 2017 19:54:03 -0400
Message-ID: <CALK=YjPSjYfF3JerZQriB86+iUT8+5Cw6qVk+boJZoK-trJv0A@mail.gmail.com>
To: users@httpd.apache.org
Content-Type: text/plain; charset="UTF-8"
Subject: Re: [users@httpd] how to get apr_pool_t when need to call ap_md5
archived-at: Thu, 07 Sep 2017 23:54:12 -0000

On Thu, Sep 7, 2017 at 12:07 PM, eeadev dev <eeadev@gmail.com> wrote:
> In my function I need to get the checksum using md5.
>
> I saw that there is this function ap_md5(apr_pool_t *a, const unsigned char
> *string);
>
> but it needs apr_pool_t
>
> how can I get it?
>
> char key[] = "abc";
>
> key_md5 = ap_md5(mem_pool, key);

Most request processing hooks are passed the request_rec which has a
pool with request lifetime.  Similar for connection-level hooks and
conn_rec.

While parsing directives, you have pools passed on the cmd_* structure
which are either temporary or very long-lived.

Finally, you can create & destroy a new pool if you are in some very weird code.

Could you elaborate on the context?

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org