Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
  • 한국 커뮤니티
0

WDDX packet parse error on CF development server

New Here ,
Oct 23, 2009 Oct 23, 2009

We have been getting an error on our development server since 10/8/09.

Error is "WDDX packet parse error at line 1, column 1. Content is not allowed in prolog."  Since this error has started, we have been unable to get the our development website to open.  Has anyone seen this error and do you know how to fix it?

7.4K
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Valorous Hero ,
Oct 23, 2009 Oct 23, 2009

Your applicaiton is trying to read and parse a WDDX packet.  This packet is not a properly formated XML WDDX data.  That code can not parse it and is throwing that error.

That is all I can tell you, but that is what the error message has already been telling you.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Oct 24, 2009 Oct 24, 2009

The error message usually suggests that there is a character (which may be a space or byte order mark) before the line <?xml version="1.0" encoding='UTF-8'?>. Assuming your encoding is the default UTF-8, you could remove any space or BOM by starting with a line similar to the following,

<cfset trimmed_packet = replace(trim(packet),chr(65279),"")>

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Aug 08, 2012 Aug 08, 2012
LATEST

I had this problem as well, however my solution was a little more simple. Some where in the code is probably a line like so:

<cfwddx action="wddx2cfml" input="someVariable" output="anotherVariable">

My problem was that someVariable needed to be wrapped like so #someVariable#

<cfwddx action="wddx2cfml" input="#someVariable#" output="anotherVariable">

This solved my problem.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Resources