Chris wrote:
I'm writing a web app that passes values in the URL separated by a / .
I'm passing these values by supplying links to them.
The writing and reading of these values is fine, I'm just stuck at the
differing ways IE handles urlencoding the data..
IE will not work unless I double urlencode
Thanks, while that solution would technically work, it doesn't appeal to
me very much.
What these values are are the primary key of a table in a database. They
are going to be primarily numbers, but I need the ability to have them
as strings as well.
I'm probably going to end up checking if th
You could base64_encode it... you'll run into url length issues at some
point, but I believe that's around 4kbytes or so...
I've done this before... something like:
base64_encode(serialize($my_object));
then undo it on the other end.
On Mon, 4 Apr 2005, Chris wrote:
I'm writing a web app that pas
I'm writing a web app that passes values in the URL separated by a / .
I'm passing these values by supplying links to them.
The writing and reading of these values is fine, I'm just stuck at the
differing ways IE handles urlencoding the data..
IE will not work unless I double urlencode it
`url
4 matches
Mail list logo