pxd119 / as3-rpclib

Automatically exported from code.google.com/p/as3-rpclib
BSD 3-Clause "New" or "Revised" License
0 stars 0 forks source link

Http Request Error with Safari #17

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Launch Sample application from
http://www.artima.com/weblogs/viewpost.jsp?thread=208528
2. Use standard Safari or Air to launch

What is the expected output? What do you see instead?

There should be text being reversed and scrambled

What version of the product are you using? On what operating system?

Error message saying that the http connection does not work. This is on
Safari 3 using OS X 10.6

Please provide any additional information below.

Note: This works on Firefox!

No amount of crossdomain.xml or tweaks could get this to work. 

Original issue reported on code.google.com by RyanAMi...@gmail.com on 31 Oct 2009 at 3:53

GoogleCodeExporter commented 8 years ago
Added png screen versions

Original comment by RyanAMi...@gmail.com on 31 Oct 2009 at 4:07

Attachments:

GoogleCodeExporter commented 8 years ago
Air example (same result)

Original comment by RyanAMi...@gmail.com on 31 Oct 2009 at 4:12

Attachments:

GoogleCodeExporter commented 8 years ago
at RyanAMills:
I ran today into same problem. I guess you use python2.6. With this version you 
have to define the 
RequestHandler path explicitly.

If you follow this example: 
http://docs.python.org/library/simplexmlrpcserver.html#simplexmlrpcserver-
example , replace: rpc_paths = ('/RPC2',) with  rpc_paths = 
('/','/RPC2','/xmlrpc')

Original comment by roet...@gmail.com on 17 Nov 2009 at 11:57

GoogleCodeExporter commented 8 years ago
Hi Ryan,

I have the same problem, running it as Air application under OS X 10.6. I even 
tried different XML-RPC Server 
(e.g. C++), but it doesn't work either. Any news on your side ?

Original comment by tinnef...@gmail.com on 1 Dec 2009 at 10:11

GoogleCodeExporter commented 8 years ago
[deleted comment]
GoogleCodeExporter commented 8 years ago
Hi Ryan,

I think I found the problem. Let's have a look at the XML that is generated 
e.g. out of AIR:

POST /RPC2null HTTP/1.1
Host: localhost:8888
Content-Type: text/xml

Here you see that /RPC2 is directly followed by null. The null is there because 
there is no destination 
specified in the XMLRPCObject. If I add an empty destination to my XMLRPCObject 
it works flawlessly.

<ak33m:XMLRPCObject id="server" endpoint="http://localhost:8000/RPC2" 
destination="">

The resulting XML now looks like:

POST /RPC2 HTTP/1.1
Host: localhost:8888
Content-Type: text/xml

See the attached screenshot, I hope that does it for you.

Best,
Christian

Original comment by tinnef...@gmail.com on 1 Dec 2009 at 11:36

Attachments:

GoogleCodeExporter commented 8 years ago
[deleted comment]
GoogleCodeExporter commented 8 years ago
Christian, thanks I had discovered that as well on a mock project I tried, but I
didn't see the connection and never retested this example. Anyways, yes, this 
appears
to work.... not documented anywhere, but putting a blank in the destination 
solves it. 

Roettig... I tried some of the path changes before, and it didn't seem to work. 
I
suppose this can be closed and the resolution being put a blank destination 
entry. 

Original comment by RyanAMi...@gmail.com on 1 Dec 2009 at 2:19