Re: [PATCH] HTTP_request

u can add to the list the buggy urlencode\decode of cookies values: " The VALUE is opaque to the user agent and may be anything the origin server chooses to send, possibly in a server-selected printable ASCII encoding. "Opaque" implies that the content is of interest and relevance only to the origin server. The content may, in fact, be readable by anyone that examines the Set-Cookie header. " (source: http://www.cis.ohio-state.edu/cgi-bin/rfc/rfc2109.html) "Alexey Borzov" <borz_off@cs.msu.su> wrote in message news:3F7A9A0A.6090407@cs.msu.su... > Hi! > > Arnaud Limbourg wrote: > > Reading this i think pear group should step up and make a decision > > concerning HTTP_Request. To me it looks like it needs a new maintainer > > (temporary ?). > > > > To avoid confusion i'm suggesting ading a new maintainer to the list, > > not removing the current maintainer and replacing him. > > Here is a quote from the mail I sent to Christian Stocker on 2003-08-07 and > received no response yet: > > =========================================================== > At the same time there are several unapplied patches floating around: > > 1) A patch I sent to Richard a lo-o-ong time ago to make appending [] to > variables optional (like the one that was applied to Net_URL) > 2) File upload patch (your own!): > > http://marc.theaimsgroup.com/?l=pear-dev&m=104799891514924&w=2 > 3) Stefan Walk's patch to implement Observer pattern and to do a lot of other > stuff. > 4) I received a patch for 100-Continue response handling for HTTP_Client. I > suspect it'll be better to implement this in HTTP_Request. > =========================================================== > > I can work on integrting the patches and preparing a new major release of > HTTP_Request, as its current state limits the possibilities of development for > my own HTTP_Client. > > There is also a problem with redirection support in HTTP_Request. My personal > POW is that redirection does not belong to the package at all and its addition > was a BC break done in a minor 1.1.1 release. > > Since the original maintainer, Richard Heyes, was briefly appearing on the lists > I'm Cc:'ing him on this.