Skip to main content
Participant
February 8, 2016
Question

cfajaxproxy results in status 500 WDDX packet parse error

  • February 8, 2016
  • 1 reply
  • 364 views

Hi.  We set up at second CF10 server, identical to the first, but the new server breaks on all cfajaxproxy calls with "Status: 500, WDDX packet parse error at line 1, column 1. Content is not allowed in prolog."  The servers are identical, completely patched and up-to-date, and everything works on the old server.

I've cleared my browser cache and temp files, checked that the return value does not have stray characters (it fails even if nothing is returned), tried returntype=plain/json/xml, asyncmode and syncmode, and turned on debugging, which only generates the same error message.

Using straight javascript to call a new XMLHttpRequest() does work, so it's something about cfajaxproxy that's failing.

Any idea what could be causing the issue?

Thank you.

This topic has been closed for replies.

1 reply

WolfShade
Legend
February 8, 2016

Sounds, to me, like the CFSCRIPT folder isn't where the CF server thinks it should be.

Just a thought.

V/r,

^_^

ShylyAuthor
Participant
February 8, 2016

Using Firebug I can see that it's hitting CFIDE\scripts\ajax\package\cfajax.js.

One thing I did notice though is that parameters aren't getting passed into the request.  That might be a red herring though, since even functions without parameters are failing.

Thanks,

Shyly