[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: SV: Parse error in httpapi



Upon further review...
Removing the a: from the elements allowed it to parse just fine.
Some of the formatters

-----Original Message-----
From: ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx [mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of Mike Krebs
Sent: Thursday, December 31, 2015 11:49 PM
To: HTTPAPI and FTPAPI Projects
Subject: RE: SV: Parse error in httpapi

I tried 4 online formatters/editors and none of them liked that piece of XML. I did not try to hand parse it but I would be confused by the <, > and &lt; trying to do that. 

Mike Krebs

-----Original Message-----
From: ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx [mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of Scott Klement
Sent: Thursday, December 31, 2015 9:48 PM
To: HTTPAPI and FTPAPI Projects
Subject: Re: SV: Parse error in httpapi

Julius,

If I remember correctly, the version of Expat in HTTPAPI actually contains the 2.0.1 updates, even though I ported it before 2.0.1. You might have noticed that some of the changes they logged for Expat were related to EBCDIC -- they got those changes from me.  I actually incorporated those changes into my copy, as well as the other fixes, before including it in HTTPAPI.  So the version in HTTPAPI is shown as 2.0.0, but it's actually 2.0.0 plus the fixes I added.  Shortly afterwards, the Expat project released 2.0.1 with the same fixes.

I see they now have 2.1.0.  I have not looked into that one.  I have not run into any need for an update, so haven't updated it.

I think before looking into this, we should determine if that update would address Magne's error.  Indeed, at this point, it's not clear to 
me what is causing the problem Magne is experiencing.   I think we 
should set up a test case and see if we can determine where things are going wrong.

If we can determine that an update to 2.1.0 will help, then I'll be happy to make one.  But, this update is not easy to do properly, so I'd like to know that it will help before doing it.  I don't see anything on http://www.libexpat.org that seems to address the situation Magne is experiencing...

-SK


On 12/31/2015 11:00 AM, Julius Kaj wrote:
> Correction!
> The current version of Expat is actually more recent (I linked to an apparently abandoned older project page):
> http://www.libexpat.org/
>
> Someone with C knowledge may be able to interpret what has been 
> changed since Scott did his IBM I port of Expat. :-)
>
>
> -----Oprindelig meddelelse-----
> Fra: ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx 
> [mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx] På vegne af Julius Kaj
> Sendt: 31. december 2015 17:20
> Til: 'HTTPAPI and FTPAPI Projects'
> Emne: SV: Parse error in httpapi
>
> Actually, according to this 
> http://stackoverflow.com/questions/1091945/what-characters-do-i-need-t
> o-escape-in-xml-documents the > character doesn't need to be escaped 
> inside an element text.
>
> The OP's XML would thus pass the W3C Markup Validation Service test and be considered valid. But the parser used (Expat?) may still require that > be escaped, though that should then be considered a bug, I think.
>
> I see that the Expat version on Scott's homepage is listed as being version 2.0.0, while the Expat site lists version 2.0.1 as the current one. The list of changes in that bugfix release doesn't directly state anything about the described scenario, but it may still be worth looking into as some of the listed fixes are pretty high-level descriptions that doesn't really say what has actually been fixed.
>
> http://expat.sourceforge.net/
> http://www.scottklement.com/expat/
>
>
>
> -----Oprindelig meddelelse-----
> Fra: ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx 
> [mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx] På vegne af Koester, 
> Michael
> Sendt: 31. december 2015 14:43
> Til: HTTPAPI and FTPAPI Projects
> Emne: RE: Parse error in httpapi
>
> I am going to guess that the trouble might be caused by the > just before "Skatteetaten"?  is that a character imbedded in the CorrespondenceTxt that needs to be escaped?
>
> I had a similar issue with a < symbol recently.
>
> Michael Koester
>
>> -----Original Message-----
>> From: ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx [mailto:ftpapi- 
>> bounces@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of Magne Kofoed
>> Sent: Wednesday, December 30, 2015 1:48 PM
>> To: ftpapi@xxxxxxxxxxxxxxxxxxxxxx
>> Subject: Parse error in httpapi
>>
>> Hi,
>>
>> I get an error (the parsing just ends - no error msg, but RC = -1) 
>> when I try to parse this tag:
>>
>> <a:CorrespondenceTxt>&lt;p>Skatteetaten har behandlet innsendingen. 
>> Du må åpne tilbakemeldingene under for å se hva du skal gjøre 
>> videre.&lt;/p></a:CorrespondenceTxt>
>>
>> Any idea on how to parse this?
>>
>> HTTPAPI_VERSION is 1.24
>>
>> Best regards,
>>
>> Magne
> ----------------------------------------------------------------------
> - This is the FTPAPI mailing list.  To unsubscribe, please go to:
> http://www.scottklement.com/mailman/listinfo/ftpapi
> ----------------------------------------------------------------------
> -
>
> ______________________________________________________________________
> This email has been scanned by the Symantec Email Security.cloud service.
> For more information please visit http://www.symanteccloud.com 
> ______________________________________________________________________
>
> ______________________________________________________________________
> This email has been scanned by the Symantec Email Security.cloud service.
> For more information please visit http://www.symanteccloud.com 
> ______________________________________________________________________
> ----------------------------------------------------------------------
> - This is the FTPAPI mailing list.  To unsubscribe, please go to:
> http://www.scottklement.com/mailman/listinfo/ftpapi
> ----------------------------------------------------------------------
> -
>
> ______________________________________________________________________
> This email has been scanned by the Symantec Email Security.cloud service.
> For more information please visit http://www.symanteccloud.com 
> ______________________________________________________________________
>
> ______________________________________________________________________
> This email has been scanned by the Symantec Email Security.cloud service.
> For more information please visit http://www.symanteccloud.com 
> ______________________________________________________________________
> ----------------------------------------------------------------------
> - This is the FTPAPI mailing list.  To unsubscribe, please go to:
> http://www.scottklement.com/mailman/listinfo/ftpapi
> ----------------------------------------------------------------------
> -
>

-----------------------------------------------------------------------
This is the FTPAPI mailing list.  To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------
-----------------------------------------------------------------------
This is the FTPAPI mailing list.  To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------
-----------------------------------------------------------------------
This is the FTPAPI mailing list.  To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------