Skip to main content

Author Topic: Bad Data in Loan - Crashing My API Client

a
  • Posts: 52
Bad Data in Loan - Crashing My API Client
OP: January 09, 2015, 12:00:00 AM
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!
  • IP logged

b
  • Posts: 152
Bad Data in Loan - Crashing My API Client
#1: January 09, 2015, 12:00:00 AM
    Other issues I've had to muddle through:

    • double quotes within double quotes in free text

    • 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)
  • IP logged

l
  • ****
  • Sr. Member
  • Posts: 325


F
  • Posts: 282
Bad Data in Loan - Crashing My API Client
#4: January 09, 2015, 12:00:00 AM
I use a CSV parser that can accept the RFC 4180 format (http://tools.ietf.org/html/rfc4180), rarely encounter crashing issues.
  • IP logged

h
  • Posts: 1
Bad Data in Loan - Crashing My API Client
#5: January 12, 2015, 12:00:00 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.
  • IP logged


  • Posts: 300
Bad Data in Loan - Crashing My API Client
#7: January 13, 2015, 12:00:00 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.

from: avid investor on January 13, 2015, 04:26:01 AM
  • IP logged