> diff -r 2a1ddbc46a89 share/hop-request.js > --- a/share/hop-request.js Sat Oct 05 07:37:26 2013 +0200 > +++ b/share/hop-request.js Mon Oct 07 17:41:15 2013 +0200 > @@@ -598,7 +598,7 @@@ > /*---------------------------------------------------------------------*/ > function hop_xdomain_onmessage( event ) { > var xhr = new Object(); > - var m = event.data.match( "([0-9]+) ([^ ]+) ([^ ]+) ([^ ]+) ([^ ]+)( *)" > ); > + var m = event.data.match( "([0-9]+) ([^ ]+) ([^ ]+) ([^ ]+)( *)" ); > > xhr.status = parseInt( m[ 1 ] ); > xhr.content_type = m[ 3 ]; > @@@ -609,7 +609,7 @@@ > > // Install a fake 'getResponseHeader' procedure to please > // 'xhr_hop_failure_callback'. > - xhr.getResponseHeader = function(h) { return null; } > + xhr.getResponseHeader = function(h) { return null; }; > > hop_request_onready( xhr, > hop_xdomain_msg[ key ].svc, > > The erroneous pattern would lead to passing truncated Javascript > strings to hop_unserialize. Ah yes. You are correct. The message content was truncated. I have probably missed that because your example was not using the value produced by the service call.
Thanks. -- Manuel btw, I have made another minor change. I have switch the argument status and key.