You are viewing a plain text version of this content. The canonical link for it is here.
Posted to apreq-dev@httpd.apache.org by Lee Goddard <ho...@LeeGoddard.com> on 2003/01/28 14:10:53 UTC

Re[2]: ap_unescape_url can't escape %uXXXX

-----BEGIN PGP SIGNED MESSAGE-----
Hash: MD5

Hi IKEBE,

On Tuesday, January 28, 2003 at 1:32:43 PM, you wrote:


IT> I have written a little patch for libapreq which unescape
IT> the %uXXXX style URI-escaped string.
IT> the unescape algorithm is based on CGI.pm

Any idea if/when that'll be incorporated to the distributions?

I currently have to have a handler check every incoming request
for failure, and then convert with Unicode::String ....

- --
Cheers
 Lee "Of course, if everyone used Lynx, this wouldn't be a problem"
 Goddard

-----BEGIN PGP SIGNATURE-----
Version: 2.6

iQCVAwUAPjaBYadrfekeF/QBAQHDJgP/YnPgGH8c3emGgbwnuvAB3B2jIvnetcD0
2nyE4ODThKoRuITHRX5qa9FvHtz2ouNM+pgDr0wo6TRyJM7sqmpzXVy/0XYw6NUV
j8nxkBiELC4F9JWyf+a91rzvTOA/eXDPizrOC9/OgKKn+ZH86GftoeNd+KvhM4TG
kRmE6bJ5O+4=
=ZPvi
-----END PGP SIGNATURE-----


Re: Re[2]: ap_unescape_url can't escape %uXXXX

Posted by Joe Schaefer <jo...@sunstarsys.com>.
Lee Goddard <ho...@LeeGoddard.com> writes:

> Any idea if/when that'll be incorporated to the distributions?
> 
> I currently have to have a handler check every incoming request
> for failure, and then convert with Unicode::String ....

It'll likely go into the next libapreq-1.X release, and be 
carried on to 2.X versions as well.  1.1 is now on its 
way to becoming official (I don't know if it'll ever 
appear on CPAN though), so there's nothing holding up further 
progress on httpd-apreq.

-- 
Joe Schaefer

Re: Re[2]: ap_unescape_url can't escape %uXXXX

Posted by Joe Schaefer <jo...@sunstarsys.com>.
Lee Goddard <ho...@LeeGoddard.com> writes:

> Any idea if/when that'll be incorporated to the distributions?
> 
> I currently have to have a handler check every incoming request
> for failure, and then convert with Unicode::String ....

It'll likely go into the next libapreq-1.X release, and be 
carried on to 2.X versions as well.  1.1 is now on its 
way to becoming official (I don't know if it'll ever 
appear on CPAN though), so there's nothing holding up further 
progress on httpd-apreq.

-- 
Joe Schaefer