Skip to content
This repository has been archived by the owner on Jul 21, 2019. It is now read-only.

Problem with parsing to json #1

Closed
shafiev opened this issue Apr 27, 2018 · 2 comments
Closed

Problem with parsing to json #1

shafiev opened this issue Apr 27, 2018 · 2 comments
Assignees

Comments

@shafiev
Copy link

shafiev commented Apr 27, 2018

I have add some debugging to catch this problem

Error was in : {"ip": "54.208.242.36", "server": "www.xxxx.com", "uri": "/market-analysis/forecast/usdjpy-2016-'"", "learning": "1", "vers": "0.56", "total_processed": "205", "total_blocked": "97", "block": "1", "cscore0": "$SQL", "score0": "12", "cscore1": "$XSS", "score1": "16", "zone0": "URL", "id0": "1001", "var_name0": "", "zone1": "URL", "id1": "1013", "var_name1": ""} ||| , or } expected while parsing object/hash, at character offset 103 (before "", "learning": "1", ...") at ./naim_lasagna.pl line 65, line 20526.
Error was in : {"ip": "54.208.242.36", "server": "www.xxx.com", "uri": "/market-analysis/\www.vulnweb.com/wtioil-2016-q1", "learning": "1", "vers": "0.56", "total_processed": "207", "total_blocked": "98", "block": "1", "cscore0": "$TRAVERSAL", "score0": "4", "zone0": "URL", "id0": "1205", "var_name0": ""} ||| illegal backslash escape sequence in string, at character offset 80 (before "\www.vulnweb.com/wt...") at ./naim_lasagna.pl line 65, line 20533.

@dmgnx dmgnx self-assigned this Apr 30, 2018
dmgnx pushed a commit that referenced this issue May 1, 2018
@dmgnx dmgnx closed this as completed in 4c22edf May 1, 2018
@shafiev
Copy link
Author

shafiev commented May 3, 2018

Anyway there problem exists with new version

, or } expected while parsing object/hash, at character offset 1564 (before ": "open+sans:300,400...") at /usr/share/perl5/JSON.pm line 171, line 81.

@dmgnx dmgnx reopened this May 3, 2018
@dmgnx dmgnx closed this as completed in 7def3f4 May 3, 2018
@dmgnx
Copy link
Owner

dmgnx commented May 3, 2018

JSON parsing replaced with an URI parser but there's still an issue with the line you emailed me. Looks like exceptions are chunked over multiple records (so much exceptions for a single endpoint ^^).
Opening a new issue.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants