| Frédéric v. Bochmann 2005-08-24, 5:53 pm |
| Yes, it often has to do with a Remoting call not working with AMFPhp.
This is often because the php has made an error and the descrambling part of
the Remoting on the FCS gets a bad header for the return he's expecting. The
AMFPhp will return an html page when an error arises, making that page not
understandable content for the FCS.
Fredz./
-----Original Message-----
From: flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
[mailto:flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org] On Behalf Of Naicu Octavian
Sent: August 24, 2005 9:38 AM
To: flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
Subject: [FlashComm] Client.Header.BadVersion ?!?!
k, I was just looking trough some logs and I noticed
this message kept popping up in the
application.onStatus() event and I discovered it
showed up when I was saving a snapshot of a camera and
called a function via AMFPhp!
Client.Header.BadVersion. I could not find any info on
it but I have resons to believe it has to do with AMFPhp!
________________________________________
____________
Start your day with Yahoo! - make it your home page
http://www.yahoo.com/r/hs
=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
|