Opened 17 years ago

Closed 12 years ago

#1969 closed Bug (wontfix)

FCKXml.LoadUrl fails on non-http pages

Reported by: Stijn Sanders Owned by:
Priority: Low Milestone:
Component: General Version:
Keywords: Cc:

Description

In Internet Explorer, using an alternative way to get to HTML pages, (e.g. a plugin implementing IInternetProtocol), for security reasons, XmlHttpRequest.responseXML is empty, but responseText works, so I generally update fckeditorcode_ie.js

"if (B.status==200
B.status==304) this.DOMDocument=B.responseXML;else if (B.status==0&&B.readyState==4){"

to

"if (B.status==200
B.status==304) this.DOMDocument=B.responseXML;if ((B.status==0&&B.readyState==4)this.DOMDocument.firstChild==null){"

to have the responseText loaded in a new document

Find this issue on GitHub

Change History (4)

comment:1 Changed 17 years ago by Bart McLeod

Same as #2087

I think you should update the source code and then compress and document your changes here.

The problem appears in both IE and Firefox if the responseXML property is empty AND the status is 200.

comment:2 in reply to:  1 Changed 17 years ago by Bart McLeod

In editor/_source/classes/fckxml_ie.js (and also fckxml_gecko.js)

use

        if ( (oXmlHttp.status == 0 && oXmlHttp.readyState == 4 )  ||  oXmlHttp.status == 200  || oXmlHttp.status == 304   )
		{
			this.DOMDocument = FCKTools.CreateXmlObject( 'DOMDocument' ) ;
			this.DOMDocument.async = false ;
			this.DOMDocument.resolveExternals = false ;
			this.DOMDocument.loadXML( oXmlHttp.responseText ) ;
		}
		else
		{
			this.DOMDocument = null ;
		}

comment:3 Changed 16 years ago by Artur Formella

Keywords: Confirmed added

comment:4 Changed 12 years ago by Piotrek Koszuliński

Resolution: wontfix
Status: confirmedclosed

Expired.

Find this issue on GitHub
Note: See TracTickets for help on using tickets.
© 2003 – 2022, CKSource sp. z o.o. sp.k. All rights reserved. | Terms of use | Privacy policy