From: Alan Gutierrez on
Andrew Poulos wrote:
> On 26/07/2010 10:01 AM, Richard Cornford wrote:
>> Andrew Poulos wrote:
>>> On 25/07/2010 3:02 PM, David Mark wrote:
>>>> On Jul 24, 11:27 pm, Alan Gutierrez wrote:
>>>>> Andrew Poulos wrote:
>>>>>> It look like the error
>>>>>> is in jquery. Of course the LMS vendor cannot give me their
>>>>>> source code. So now I'll be caught between an client and a
>>>>>> (most likely) quick-stepping LMS vendor.
>>>>>
>>>>> Is their source code obfuscated? What is the error?
>>>>
>>>> He already said what the error was and Richard pointed out
>>>> how to track it down (obfuscated or not).
>>>
>>> I think I need to retract my assertion that jquery was the cause
>>> of the issue I was experiencing.
>>>
>>> Using Charles I see that there's a "500 Internal Server Error"
>>> and that "Failed to parse data (org.xml.sax.SAXParseException:
>>> Open quote is expected for attribute..."
>>
>> Server error responses often have an HTML body, though Charles really
>> should not be presenting that to an XML parser (which is what SAX is)
>> unless the response includes a content-type header that says the body is
>> XML (which would include XHTML, SOAP, etc.).
>>
>> An attempt to - eval - such a response body is the sort of thing that
>> may produce a "... is undefined" error, though that is less likely than
>> it producing a syntax error. And it would be odd for any client-side
>> software to respond to an HTTP status of 500 by attempting to - eval -
>> the response body.
>>
>> Still, Charles offers the response in raw, text, hex, and headers form
>> in addition to parsed XML so you can see all of the error response.
>>
>>> So it seems its something in the LMS Vendor's Server???
>>
>> Assuming that the request parameters were correct, as seeing the LMS
>> system sending error responses to erroneous requests would not
>> necessarily represent a fault in the LMS system.
>
> Testing in the ADL test suites confirms that appropriate data in the
> appropriate format is being sent at the appropriate time.
>
> With a bit more error checking and I find that a response from the
> server contains is
>
> <?xml version='1.0' encoding='ISO-8859-1'?>
> <values>
> <group>
> <lasterror></lasterror>
> <returnvalue><![CDATA[]]></returnvalue>
> </group>
> </values>

If that is the entire message, then it is well formed according to
`xmllint`.

> and the corresponding error is
>
> Error: not well-formed
> Source File: http://www.blah.com.au/Host/scorm1.2server.asp
> Line: 1
> Column: 26
> Source Code: <font face="Arial" size=2>

Must be a different response, since that source does not exist in the
response above.

> This error is followed by this error:
>
>
> Error: xmlDoc.getElementsByTagName("returnvalue")[0] is undefined
> Source File:
> http://www.blah.com.au/Host/scorm1.2api.asp?loadURL=SCORM_courses/tp/intermediate/index.htm&anchor=
>
> Line: 161
>
>
> I can see how if the XML was not well formed why the error would occur
> but not why the response doesn't appear to me to contain
> "<font face="Arial" size=2>"

Something is not right, but I can't tell what. The document returned
parses correctly, so it is odd that `getElementsByTagName` cannot find
the element, but there is a lot of context missing.

What happened the `SAXException`? That was the most promising.

--
Alan Gutierrez - alan(a)blogometer.com - http://twitter.com/bigeasy
From: David Mark on
On Jul 25, 9:50 pm, David Mark <dmark.cins...(a)gmail.com> wrote:
> On Jul 25, 9:33 pm, Andrew Poulos <ap_p...(a)hotmail.com> wrote:
>
>
>
>
>
> > On 26/07/2010 10:01 AM, Richard Cornford wrote:
>
> > > Andrew Poulos wrote:
> > >> On 25/07/2010 3:02 PM, David Mark wrote:
> > >>> On Jul 24, 11:27 pm, Alan Gutierrez wrote:
> > >>>> Andrew Poulos wrote:
> > >>>>> It look like the error
> > >>>>> is in jquery. Of course the LMS vendor cannot give me their
> > >>>>> source code. So now I'll be caught between an client and a
> > >>>>> (most likely) quick-stepping LMS vendor.
>
> > >>>> Is their source code obfuscated? What is the error?
>
> > >>> He already said what the error was and Richard pointed out
> > >>> how to track it down (obfuscated or not).
>
> > >> I think I need to retract my assertion that jquery was the cause
> > >> of the issue I was experiencing.
>
> > >> Using Charles I see that there's a "500 Internal Server Error"
> > >> and that "Failed to parse data (org.xml.sax.SAXParseException:
> > >> Open quote is expected for attribute..."
>
> > > Server error responses often have an HTML body, though Charles really
> > > should not be presenting that to an XML parser (which is what SAX is)
> > > unless the response includes a content-type header that says the body is
> > > XML (which would include XHTML, SOAP, etc.).
>
> > > An attempt to - eval - such a response body is the sort of thing that
> > > may produce a "... is undefined" error, though that is less likely than
> > > it producing a syntax error. And it would be odd for any client-side
> > > software to respond to an HTTP status of 500 by attempting to - eval -
> > > the response body.
>
> > > Still, Charles offers the response in raw, text, hex, and headers form
> > > in addition to parsed XML so you can see all of the error response.
>
> > >> So it seems its something in the LMS Vendor's Server???
>
> > > Assuming that the request parameters were correct, as seeing the LMS
> > > system sending error responses to erroneous requests would not
> > > necessarily represent a fault in the LMS system.
>
> > Testing in the ADL test suites confirms that appropriate data in the
> > appropriate format is being sent at the appropriate time.
>
> Okay.
>
>
>
> > With a bit more error checking and I find that a response from the
> > server contains is
>
> > <?xml version='1.0' encoding='ISO-8859-1'?>
> > <values>
> >    <group>
> >      <lasterror></lasterror>
> >        <returnvalue><![CDATA[]]></returnvalue>
> >    </group>
> > </values>
>
> Fairly useless blob of XML.  :)
>
>
>
> > and the corresponding error is
>
> > Error: not well-formed
> > Source File:http://www.blah.com.au/Host/scorm1.2server.asp
> > Line: 1
> > Column: 26
> > Source Code: <font face="Arial" size=2>
>
> IIS generates that silly opening font tag on canned responses.
>
>
>
> > This error is followed by this error:
>
> > Error: xmlDoc.getElementsByTagName("returnvalue")[0] is undefined
> > Source File:http://www.blah.com.au/Host/scorm1.2api.asp?loadURL=SCORM_courses/tp/...
> > Line: 161
>
> Clearly the returned XML has no such element.  The client side script
> should accomodate that (but doesn't here).
>

Oops, I misread. That element is in the XML quoted above. So that's
not the XML the client-side script was dealing with at the time of the
exception.
From: David Mark on
On Jul 25, 10:24 pm, Alan Gutierrez <a...(a)blogometer.com> wrote:
> Andrew Poulos wrote:
> > On 26/07/2010 10:01 AM, Richard Cornford wrote:
> >> Andrew Poulos wrote:
> >>> On 25/07/2010 3:02 PM, David Mark wrote:
> >>>> On Jul 24, 11:27 pm, Alan Gutierrez wrote:
> >>>>> Andrew Poulos wrote:
> >>>>>> It look like the error
> >>>>>> is in jquery. Of course the LMS vendor cannot give me their
> >>>>>> source code. So now I'll be caught between an client and a
> >>>>>> (most likely) quick-stepping LMS vendor.
>
> >>>>> Is their source code obfuscated? What is the error?
>
> >>>> He already said what the error was and Richard pointed out
> >>>> how to track it down (obfuscated or not).
>
> >>> I think I need to retract my assertion that jquery was the cause
> >>> of the issue I was experiencing.
>
> >>> Using Charles I see that there's a "500 Internal Server Error"
> >>> and that "Failed to parse data (org.xml.sax.SAXParseException:
> >>> Open quote is expected for attribute..."
>
> >> Server error responses often have an HTML body, though Charles really
> >> should not be presenting that to an XML parser (which is what SAX is)
> >> unless the response includes a content-type header that says the body is
> >> XML (which would include XHTML, SOAP, etc.).
>
> >> An attempt to - eval - such a response body is the sort of thing that
> >> may produce a "... is undefined" error, though that is less likely than
> >> it producing a syntax error. And it would be odd for any client-side
> >> software to respond to an HTTP status of 500 by attempting to - eval -
> >> the response body.
>
> >> Still, Charles offers the response in raw, text, hex, and headers form
> >> in addition to parsed XML so you can see all of the error response.
>
> >>> So it seems its something in the LMS Vendor's Server???
>
> >> Assuming that the request parameters were correct, as seeing the LMS
> >> system sending error responses to erroneous requests would not
> >> necessarily represent a fault in the LMS system.
>
> > Testing in the ADL test suites confirms that appropriate data in the
> > appropriate format is being sent at the appropriate time.
>
> > With a bit more error checking and I find that a response from the
> > server contains is
>
> > <?xml version='1.0' encoding='ISO-8859-1'?>
> > <values>
> >   <group>
> >     <lasterror></lasterror>
> >       <returnvalue><![CDATA[]]></returnvalue>
> >   </group>
> > </values>
>
> If that is the entire message, then it is well formed according to
> `xmllint`.

That's not the response in question.

>
> > and the corresponding error is
>
> > Error: not well-formed
> > Source File:http://www.blah.com.au/Host/scorm1.2server.asp
> > Line: 1
> > Column: 26
> > Source Code: <font face="Arial" size=2>
>
> Must be a different response, since that source does not exist in the
> response above.

Right.

>
> > This error is followed by this error:
>
> > Error: xmlDoc.getElementsByTagName("returnvalue")[0] is undefined
> > Source File:
> >http://www.blah.com.au/Host/scorm1.2api.asp?loadURL=SCORM_courses/tp/....
>
> > Line: 161
>
> > I can see how if the XML was not well formed why the error would occur
> > but not why the response doesn't appear to me to contain
> > "<font face="Arial" size=2>"
>
> Something is not right, but I can't tell what. The document returned
> parses correctly, so it is odd that `getElementsByTagName` cannot find
> the element, but there is a lot of context missing.

Clearly the client-side exception was not dealing with the quoted XML.
From: Alan Gutierrez on
David Mark wrote:
> On Jul 25, 9:33 pm, Andrew Poulos <ap_p...(a)hotmail.com> wrote:

>> Error: not well-formed
>> Source File:http://www.blah.com.au/Host/scorm1.2server.asp
>> Line: 1
>> Column: 26
>> Source Code: <font face="Arial" size=2>
>
> IIS generates that silly opening font tag on canned responses.

Learn something new every day.

--
Alan Gutierrez - alan(a)blogometer.com - http://twitter.com/bigeasy
From: David Mark on
On Jul 25, 10:57 pm, Alan Gutierrez <a...(a)blogometer.com> wrote:
> David Mark wrote:
> > On Jul 25, 9:33 pm, Andrew Poulos <ap_p...(a)hotmail.com> wrote:
> >> Error: not well-formed
> >> Source File:http://www.blah.com.au/Host/scorm1.2server.asp
> >> Line: 1
> >> Column: 26
> >> Source Code: <font face="Arial" size=2>
>
> > IIS generates that silly opening font tag on canned responses.
>
> Learn something new every day.
>

I assume you don't use classic ASP (or lead a very charmed life). Any
uncaught exception in the server side script will result in a response
that opens with that tag.
First  |  Prev  |  Next  |  Last
Pages: 1 2 3 4 5
Prev: JQuery Ajax
Next: Celexa 10 mg, 5mg Celexa, Celexa acne