I’ve been struggling to figure out the issue with my Lucee install for
about a week and can’t seem to crack this one. I’m running Lucee 4.5.1.023
on AWS/Ubuntu 14.04.3 LTS.
Lucee serves .cfm pages just fine, but whenever I use a CFC, even with no
output, I get the following on Firefox “XML Parsing Error: not well-formed”
and on Chrome I get “error on line 28 at column 2527: xmlParseEntityRef: no
name”
CFC that generates the issue is as follows:
The following shows the same problem:
I’ve tried changing various settings in the server configuration output
section and whitespace management, but the error persists.
I had this issue on Railo a while back and was able to fix it by rolling
back to an earlier version of Railo. I tried rolling back to the earliest
Lucee version, but my guess is the issue was created before Railo was
forked to Lucee.
Any assistance / direction / ideas would be greatly appreciated. If I don’t
get this solved soon I’m going to have to restart my project on Railo which
I’d rather not do.
TIA - Scott
I’ve been struggling to figure out the issue with my Lucee install for
about a week and can’t seem to crack this one. I’m running Lucee 4.5.1.023
on AWS/Ubuntu 14.04.3 LTS.
Lucee serves .cfm pages just fine, but whenever I use a CFC, even with no
output, I get the following on Firefox “XML Parsing Error: not well-formed”
and on Chrome I get “error on line 28 at column 2527: xmlParseEntityRef:
no name”
CFC that generates the issue is as follows:
The following shows the same problem:
I’ve tried changing various settings in the server configuration output
section and whitespace management, but the error persists.
I had this issue on Railo a while back and was able to fix it by rolling
back to an earlier version of Railo. I tried rolling back to the earliest
Lucee version, but my guess is the issue was created before Railo was
forked to Lucee.
Any assistance / direction / ideas would be greatly appreciated. If I
don’t get this solved soon I’m going to have to restart my project on Railo
which I’d rather not do.
It really looks like it’s something to do with CFC’s output are defaulting
to XML versus HTML. When I add &returnformat=json to my URL, I get what I’d
expect.On Tuesday, August 11, 2015 at 7:41:27 AM UTC-5, scottdritz wrote:
TIA - Scott