on 1/18/01 12:48 PM, Enrique Vega at [EMAIL PROTECTED] wrote:
> Can I get any advice on how I can fix this problem without upgrading to a
> newer version of apache? If not, how would I go about doing the upgrade
> without screwing things up on my RaQ3 server?
Well, I haven't heard back on this, but I did a little digging and come to
find out that "ap_pbase64decode" was added to Apache 1.3.9. See below for
upgrade info:
Changes with Apache 1.3.9
*) Fix (re)naming in the uuencode/decode section. The ap/ap_
routines are now called ap_base64* and are 'plain' (i.e., no
pool access or anything clever). Inside util.c the routines acting
like pstrdup are called ap_pbase64encode() and ap_pbase64decode().
The oddly named ap_uuencode(), ap_uudecode() are kept around for
now but deprecated. [dirkx]
This bugs me a little because now I will not be able to upgrade due to the
current version - apache-1.3.6-C11 on the RaQ3...
More to come on version issues in a separate message...
enrique
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
