Mailing-List: contact modules-dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: modules-dev@httpd.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
Date: Mon, 10 Dec 2007 22:39:10 +0000
From: ed <ed-http@s5h.net>
To: modules-dev@httpd.apache.org
Subject: Re: Fwd:Re: http-redirect url gets corrupted in request_rec - apach
Message-ID: <20071210223910.12392ad3@workstation>
In-Reply-To: <2960_7724_1197309651_24@inet3p057p>
References: <2960_7724_1197309651_24@inet3p057p>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary=Sig_w6oVT7l7mqY6DF9Eel.SdfK;
 protocol="application/pgp-signature"; micalg=PGP-SHA1

--Sig_w6oVT7l7mqY6DF9Eel.SdfK
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

On Mon, 10 Dec 2007 13:00:51 -0500
"SAILESH KRISHNAMURTI, BLOOMBERG/ 731 LEXIN"
<skrishnamur1@bloomberg.net> wrote:

> could it also have somthing to do with the way '/'s are handled in
> 64bit versus 32 bit env. If my memory is right, these characters
> always seem to start from the '/' position.=20

The character sets are the same on both processor architectures. If
they differed then all characters would have an issue. Unless I am
mistaken there is no reason for ASCII 47 to have a different position
on the ASCII table for a 32bit proc.

What might differ is wide characters, which might take 64 bits to
represent it's position.

--=20
The T3 to www.mydigitalvoid.com is unreliable because of a memory leak
in the lyris server. The Rebel Alliance is port scanning the entire /16.
:: http://www.s5h.net/ :: http://www.s5h.net/gpg.html

--Sig_w6oVT7l7mqY6DF9Eel.SdfK
Content-Type: application/pgp-signature; name=signature.asc
Content-Disposition: attachment; filename=signature.asc

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFHXcAO4dyr7s6PRYgRAkHmAJ43XcvEMSQoZ10F87F+Y5+KRwzO/wCfaW/T
2mICKQes0DjNKQ2zNmBXSPo=
=ytPr
-----END PGP SIGNATURE-----

--Sig_w6oVT7l7mqY6DF9Eel.SdfK--