is it possible to post objects

[jbegham]

Hi group,

I just have the following situation.

After checking some data within a "process page", I want to redirect to the ongoing php-page.

the variables I checked are stored in an Object.
The redirect uses the code (reduced to example):

// Page 1
class A {
...
  function helloWorld () {
     ...
  }
}

$testObj = &new A();

$aktObject = serialize($testObj);

header("Location: nextpage.php?myObject=".$aktObject);exit;

If I pass this scenario to the next page and there unserialize the object the way:

// Page 2
class A {
  ...
}

$newObj = unserialize($_REQUEST["myObject"]);
$newObj->helloWorld();

... than the compiler stops with: "Fatal error: Call to a member function on a non-object ..."

Isn't this possible. Does anyone of you have any ideas?

TIA
John

[IceD]

Try to use "urlencode(serialize($obj))" and "unserialize(urldecode($_REQUEST["obj"]))"

[MrAlaska]

The code you posted worked fine on my machine. If IceD's suggestion does not work, I am wondering if it might be a magic quotes problem or something. Try echoing back your serialized object on each page and comparing the strings.

[jbegham]

Thank you both of you for the fast answer,

I just have tested the first thing with making an urlencodeing first. But after this, the page could not be loaded "file not found".

after removing the "?myobject=" part everything goes like it should. It seems that the urlencoded string of the serialized object generetes something, the browser does not like.

I will test the echoing-idea the get the bug 🙂

Thanks again
John

[IceD]

To MrAlaska:
Strange... I've mirrored situation...
And once again we have problem with all this magic quotes and other funny PHP features. Bgrh.

[jbegham]

I just have tried several things, all without success. Anything went wrong with the serialisation, but I could not figure out what.
Event the tests with the reduced example lead to the same error (FATAL ERROR...).

I will now use a session-var to transfer the data over the orbit while the post-car is taking the street :-)

Thanks again
John

[MrAlaska]

Originally posted by jbegham
Event the tests with the reduced example lead to the same error (FATAL ERROR...).

Instead of unserializing it, just echo it and see what is being passed.

Using session vars is cheating 😃

[jbegham]

you are right mrA - it's a bit of cheating, at least because I did not tried the magic quotes thing.

I re-tested the whole solution with echoing the passed stuff and then recognized the following.

Page 1:
1. I just serialized the object
2. urlencoded it
3. Make the re-direct ( header("Location: ...."; )

Page 2:
The echo of the POST-Var shows the
1. immediately urldecoded string (I did not urldecoded it, but it already was!)
2. All the doublequotes had a leading backslash ( \" )
3. after stripslash'ed the POST-var and unserialized it, it works

😕 But there are still remaining 2 unanswered questions left:

1. If you have an urlencoded string which will be posted by the header("Location..") syntax, why is it autmatically urlencoded? I have echoed the variable in page 1 - is WAS urlencoded - all quote characters where escaped with %22.
   It does not matter whether you urlencode it or not!

2. Why do the quotes have the leading slash where you have first run a stripslash command?

Any ideas?
Greets
John

[MrAlaska]

Originally posted by jbegham

1. If you have an urlencoded string which will be posted by the header("Location..") syntax, why is it autmatically urlencoded? I have echoed the variable in page 1 - is WAS urlencoded - all quote characters where escaped with %22.
   It does not matter whether you urlencode it or not![/B]

Proper browser behavior is to automatically url-encode, then deliver the an automatically decoded product as a GET. Or maybe it is up to PHP to decode it, I cannot recall offhand

Originally posted by jbegham
2. Why do the quotes have the leading slash where you have first run a stripslash command?

; Magic quotes
magic_quotes_gpc=On
; magic quotes for incoming GET/POST/Cookie data

I suggest turning them off, unless you might end up on a shared server that has them on and you need to deal with it. They are provided to protect you, though, so you will need to add your own slashes when there is a chance an incoming value might cause problems for you.

[IceD]

Once again about magic_quotes... If you can't turn them off (or your hosting provider don't wnat to do this), use this simple code:

$data = get_magic_quotes_gpc() ? stripslashes($_GET["data"]) : $_GET["data"];