Author Topic: Bad Data in Loan - Crashing My API Client  (Read 3236 times)

avid investor

  • Full Member
  • ***
  • Posts: 168
    • View Profile
Bad Data in Loan - Crashing My API Client
« on: January 09, 2015, 04:28:46 PM »
Multi-byte characters in the empTitle field of loan ID 38509961 is crashing my UTF-8 dependent client process.  Apparently this data is not checked when borrowers have finger-fumbles in applying for a loan.  Beware.  Hope he gets funded/rejected soon!

brycemason

  • Hero Member
  • *****
  • Posts: 801
    • View Profile
    • P2P-Picks.com
    • Email
Re: Bad Data in Loan - Crashing My API Client
« Reply #1 on: January 09, 2015, 04:52:31 PM »
    Other issues I've had to muddle through:

    • double quotes within double quotes in free text
    • \n\r within free text
    • double quotes being in the header row in REST but not in SOAP or CSV
    • free text being different between CSV and API versions (CSV cuts out special characters)

lascott

  • Hero Member
  • *****
  • Posts: 1436
    • View Profile
    • Appreciate my post and want to try LendingRobot? URL below
Re: Bad Data in Loan - Crashing My API Client
« Reply #2 on: January 09, 2015, 04:53:25 PM »
Multi-byte characters in the empTitle field of loan ID 38509961 is crashing my UTF-8 dependent client process.  Apparently this data is not checked when borrowers have finger-fumbles in applying for a loan.  Beware.  Hope he gets funded/rejected soon!
UTF-8 supports multiple bytes so your comments are confusing. Maybe you are saying the support you implemented only support the basic latin / ASCII equivalent characters. http://en.wikipedia.org/wiki/Basic_Latin_%28Unicode_block%29
Tools I use: (main) BlueVestment: https://www.bluevestment.com/app/pricing + https://www.interestradar.com/ , (others) Lending Robot referral link: https://www.lendingrobot.com/ref/scott473/  & Peercube referral code: DFVA9Y

avid investor

  • Full Member
  • ***
  • Posts: 168
    • View Profile
Re: Bad Data in Loan - Crashing My API Client
« Reply #3 on: January 09, 2015, 05:00:04 PM »
    Other issues I've had to muddle through:

    • double quotes within double quotes in free text
    • \n\r within free text
    • double quotes being in the header row in REST but not in SOAP or CSV
    • free text being different between CSV and API versions (CSV cuts out special characters)
It would be nice if they cleaned their data before posting.

Fred

  • Hero Member
  • *****
  • Posts: 1421
    • View Profile
Re: Bad Data in Loan - Crashing My API Client
« Reply #4 on: January 09, 2015, 05:51:04 PM »
I use a CSV parser that can accept the RFC 4180 format (http://tools.ietf.org/html/rfc4180), rarely encounter crashing issues.
« Last Edit: January 09, 2015, 06:07:44 PM by Fred »

heateds22

  • Newbie
  • *
  • Posts: 12
    • View Profile
    • Email
Re: Bad Data in Loan - Crashing My API Client
« Reply #5 on: January 12, 2015, 08:38:40 PM »
Why is it causing your program to fail? I don't see my client failing because of this ... Maybe you are using XML here? If so, I would suggest using JSON response as it is simple key value pairs.

avid investor

  • Full Member
  • ***
  • Posts: 168
    • View Profile
Re: Bad Data in Loan - Crashing My API Client
« Reply #6 on: January 13, 2015, 04:26:01 AM »
Why is it causing your program to fail? I don't see my client failing because of this ... Maybe you are using XML here? If so, I would suggest using JSON response as it is simple key value pairs.
No, I jumped on the JSON as soon as it was available.  You won't see the problem now as the loan has funded and isn't available anymore.  Of course, the problem could return.  The loan ID was 38509961, and the offending data was in the empTitle field.

AnilG

  • Hero Member
  • *****
  • Posts: 1120
    • View Profile
    • PeerCube
Re: Bad Data in Loan - Crashing My API Client
« Reply #7 on: January 13, 2015, 05:14:47 AM »
What was offending data in empTitle? It just says kitchen che f. https://www.peercube.com/comment?loanid=38509961

I use JSON and API and I don't see any issue. It might be how you may be parsing data.

:)
No, I jumped on the JSON as soon as it was available.  You won't see the problem now as the loan has funded and isn't available anymore.  Of course, the problem could return.  The loan ID was 38509961, and the offending data was in the empTitle field.
---
Anil Gupta
PeerCube Thoughts blog https://www.peercube.com/blog
PeerCube https://www.peercube.com