Are there any know issues with Lucee 5.4.3.2 with XML files. I'm banging my head against a brick wall here. I have the exact same configuration and setup on both the CF server that I am migrating too and the Lucee server. I have gone through all the server settings etc with a fine tooth comb. The CF version works as it should but on the Lucee version i keep getting this frustrating error! Arghhhh its driving me me insane. I did post a message the other day and have gone through absolutely everything I can think of but it just does not recognise the XML file - its fine on CF with the exact same setup and codebase. If anyone can spare some time to assist I would be extremely grateful.

This XML file does not appear to have any style information associated with it. The document tree is shown below.

hometrack realtime accountid="-1" valuationresponse errors error errorid="63" errormessage="Unrecognised XML Format - please check schema"/ /errors /valuationresponse /realtime /hometrack

DO you have any comments in the XML document? Specifically at the 1st line? Also - There is a security "fix" where <!DOCTYPE> declarations are an issue. CVE-2023-38693 Subsequently changes were made to Lucee to address this and as a DEFAULT lucee no longer allows <!DOCTYPE> declarations in XML. I removed my DOCTYPE definitions to get my code running.

Same as last time. Yer not really giving us much to go on here. No code. no steps to reproduce. Fairly vague expectations. How do you reasonably expect us to be able to help here?

Are there any know issues with Lucee 5.4.3.2 with XML files

Did this start going wrong in 5.4.3.2? Given the nebulous content of your question, it's kinda difficult to say "well there's this issue

[x]

in a situation

[y]

where

[z]

happens", because you have not given us the starting point

[x]

good call @gavinbaumanis I'll check that out 🙏

changes were made to Lucee to address this and as a DEFAULT lucee no longer allows <!DOCTYPE> declarations in XML.

They did what?

I'm afarid thats all I have though @Adam Cameron Ive been debugging this to the hilt and back but getting nowhere

You don't have any XML? You don't have any code?

The payload appears to get sent and it comes back but it doesnt recognise the response

You don't have a way of showing us what you're talking about?

Probably easier on a screen share tbh as tricky to explain and not doinga good job explaining it 😜

This is why one should start with a SSCCE

yes i think so 🤔

Did you read those links I think I sent you last time?

Could this issue @gavinbaumanis just reported have an impact - worth checking that too I guess

OK so haven't yet confirmed... you are doing a cfhttp req, getting a resonse that is XML, and Lucee errors when parsing the xml?

yes thats it 🙂

OK

yes thats right Adam cf parses it fine no probs

Right so move to the next step (the code example I posted above)

Lucee 6.0.0.585 Error (org.xml.sax.SAXException)Messageorg.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 1; Premature end of file.StacktraceThe Error Occurred in C\Projects\Zoopla\RealtimeLucee\root\Coldfusion\Fusebox\realtime\currentbuild\fbx Settings.cfm line 149

147: <cfsavecontent variable="s"><your><xml>here</xml></your></cfsavecontent>

148:

149: <cfset x = xmlParse(s)>

150: <cfdump var="#x#">

151: <cfaborT>

Interesting. I mean I did not intend you to run my exact example (I thought the same XML was pretty clear on that), but it's interesting it breaks on 6. it does not break on 6-beta on trycf https://trycf.com/gist/bddbbb4d8c4b79149e4e9530e936eb5c/lucee6-beta?theme=monokai TBH I would not touch Lucee 6 for another 3-6 months until other gullible saps have put it into production and "all" its issue have surfaced.

ah ok oops. ill roll back then

Just my opinion. I'd say the same for the latest version of CF too btw. That's not solely a slight on Lucee.

perhaps fbx_settings.cfm not best place to put that example?

Reproduce THAT in a stand-alone file. I know you can't share that, but factor out everything else, and just do those two lines.

ok will do

No seriously, don't run it through your app. Run it completely stand-alone

sure ok will do

Put it in

test.cfm

in a subdir with a minimal

Application.cfc

(just

component {}

), and call http://whatevs/path/to/test.cmf

ok cheers Adam ill give that a try

I'm flicking between this and my work machine... but need to focus on work for a bit. I'll keep an eye on progress here though

sure ok thanks Adam no probs at all - that file is fine just run it now

OK, so next in your test file... make that cfhttp call, and dump out its response.

ok cool will do

Any progress?

Hey Adam no not yet was pulled into something else

Interesting! Did my approach to troubleshooting help?

yes it absolutely did . Thanks :-)🙏

yay!

This was part of the problem too @Adam Cameron BUT is this only an issue in Lucee version 5.3.7.47 https://www.bennadel.com/blog/4031-expected-and-unexpected-getbasetagdata-behavior-in-lucee-cfml-5-3-7-47.htm

More importantly, doesn't 5.3.7.47 have unpatched significant CVEs? I thought 5.3.9.170 was the lowest safe (ish) version of 5.3? But yeah that bites.

yeah still broke on 5.4.3.2

Um, no, I've never had to use custom tags really, but skimming Ben's article, isn't it only an issue if using

<cfmodule>

rather than

<cf_whatevs>

? Or am I skimming too lightly? Also how does this relate to your originally-asked Q which was about

<cfhttp>

and XML?

yep unfortunately the app is 😞 using cfmodule and customtags- ah no different from that

OK, well let's stick to one issue per thread, yeah?

yes Boss 😁

Don't encourage me 😉 Nah but seriously, someone might know about custom tags and this issue, but they'll never see it in a thread about XML weirdness, is all.