Yes it's wrong Data format. "Date":"Thu Jul 19 11:30:33 2018
2018-07-19 19:00 GMT+03:00 <users-requ...@lists.opensips.org>: > Send Users mailing list submissions to > users@lists.opensips.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > or, via email, send a message with subject or body 'help' to > users-requ...@lists.opensips.org > > You can reach the person managing the list at > users-ow...@lists.opensips.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Users digest..." > > > Today's Topics: > > 1. Re: mi_json returns invalid JSON (Răzvan Crainea) > 2. Re: mi_json returns invalid JSON (Ben Newlin) > 3. Re: mi_json returns invalid JSON (Ben Newlin) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 19 Jul 2018 10:14:37 +0300 > From: Răzvan Crainea <raz...@opensips.org> > To: users@lists.opensips.org > Subject: Re: [OpenSIPS-Users] mi_json returns invalid JSON > Message-ID: <04329915-bc6d-0b21-547f-c114ccca3...@opensips.org> > Content-Type: text/plain; charset=utf-8; format=flowed > > Hi, Kirill! > > This doesn't seem to be an invalid JSON, but only a bad formatting of > the date. I agree it should not include the "\n", because it is useless, > but this doesn't make it invalid. Are you experiencing trouble with > using JSON libraries that don't support this format? > > Best regards, > Răzvan > > On 07/17/2018 12:58 PM, Kirill Galinurov wrote: > > Hi. I use opensips mi_json module to get statistics. > > But for some commands it returns incorrect JSON. > > For example /json/dr_reload_status returns > > > > {"Partition": [{"value":"sipprovider_def", "attributes":{"Date": "Mon > > Jul 16 07:10:58 2018 > > "}}, {"value":"beeline", "attributes":{"Date": "Mon Jul 16 07:11:59 2018 > > "}}, {"value":"megafon", "attributes":{"Date": "Mon Jul 16 07:11:59 2018 > > "}}, {"value":"megafon", "attributes":{"Date": "Mon Jul 16 07:12:54 2018 > > "}}, {"value":"mts", "attributes":{"Date": "Mon Jul 16 07:12:54 2018 > > "}}, {"value":"mts", "attributes":{"Date": "Mon Jul 16 07:13:51 2018 > > "}}, {"value":"beeline", "attributes":{"Date": "Mon Jul 16 07:13:52 2018 > > "}}]} > > > > This is incorrect, because it shoulde not include "\n" symbols. > > > > > > _______________________________________________ > > Users mailing list > > Users@lists.opensips.org > > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > > -- > Răzvan Crainea > OpenSIPS Core Developer > http://www.opensips-solutions.com > > > > ------------------------------ > > Message: 2 > Date: Thu, 19 Jul 2018 12:58:24 +0000 > From: Ben Newlin <ben.new...@genesys.com> > To: OpenSIPS users mailling list <users@lists.opensips.org> > Subject: Re: [OpenSIPS-Users] mi_json returns invalid JSON > Message-ID: <e8bdb991-e1a9-41b1-8d66-6a7f149ff...@genesys.com> > Content-Type: text/plain; charset=UTF-8 > > I believe newline characters used within JSON must be escaped. So if the > JSON actually contains "\n" that is invalid. It must be "\\n". > > Ben Newlin > > On 7/19/18, 3:19 AM, "Users on behalf of Răzvan Crainea" < > users-boun...@lists.opensips.org on behalf of raz...@opensips.org> wrote: > > Hi, Kirill! > > This doesn't seem to be an invalid JSON, but only a bad formatting of > the date. I agree it should not include the "\n", because it is > useless, > but this doesn't make it invalid. Are you experiencing trouble with > using JSON libraries that don't support this format? > > Best regards, > Răzvan > > On 07/17/2018 12:58 PM, Kirill Galinurov wrote: > > Hi. I use opensips mi_json module to get statistics. > > But for some commands it returns incorrect JSON. > > For example /json/dr_reload_status returns > > > > {"Partition": [{"value":"sipprovider_def", "attributes":{"Date": > "Mon > > Jul 16 07:10:58 2018 > > "}}, {"value":"beeline", "attributes":{"Date": "Mon Jul 16 07:11:59 > 2018 > > "}}, {"value":"megafon", "attributes":{"Date": "Mon Jul 16 07:11:59 > 2018 > > "}}, {"value":"megafon", "attributes":{"Date": "Mon Jul 16 07:12:54 > 2018 > > "}}, {"value":"mts", "attributes":{"Date": "Mon Jul 16 07:12:54 2018 > > "}}, {"value":"mts", "attributes":{"Date": "Mon Jul 16 07:13:51 2018 > > "}}, {"value":"beeline", "attributes":{"Date": "Mon Jul 16 07:13:52 > 2018 > > "}}]} > > > > This is incorrect, because it shoulde not include "\n" symbols. > > > > > > _______________________________________________ > > Users mailing list > > Users@lists.opensips.org > > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > > -- > Răzvan Crainea > OpenSIPS Core Developer > http://www.opensips-solutions.com > > _______________________________________________ > Users mailing list > Users@lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > > ------------------------------ > > Message: 3 > Date: Thu, 19 Jul 2018 13:03:09 +0000 > From: Ben Newlin <ben.new...@genesys.com> > To: OpenSIPS users mailling list <users@lists.opensips.org> > Subject: Re: [OpenSIPS-Users] mi_json returns invalid JSON > Message-ID: <ea885c6a-2909-4210-a99a-b54d52334...@genesys.com> > Content-Type: text/plain; charset=UTF-8 > > Actually, after further investigation I'm no longer sure that is true. > According to http://www.json.org/ the "\n" is valid in JSON. > > Ben Newlin > > On 7/19/18, 8:58 AM, "Ben Newlin" <ben.new...@genesys.com> wrote: > > I believe newline characters used within JSON must be escaped. So if > the JSON actually contains "\n" that is invalid. It must be "\\n". > > Ben Newlin > > On 7/19/18, 3:19 AM, "Users on behalf of Răzvan Crainea" < > users-boun...@lists.opensips.org on behalf of raz...@opensips.org> wrote: > > Hi, Kirill! > > This doesn't seem to be an invalid JSON, but only a bad formatting > of > the date. I agree it should not include the "\n", because it is > useless, > but this doesn't make it invalid. Are you experiencing trouble > with > using JSON libraries that don't support this format? > > Best regards, > Răzvan > > On 07/17/2018 12:58 PM, Kirill Galinurov wrote: > > Hi. I use opensips mi_json module to get statistics. > > But for some commands it returns incorrect JSON. > > For example /json/dr_reload_status returns > > > > {"Partition": [{"value":"sipprovider_def", "attributes":{"Date": > "Mon > > Jul 16 07:10:58 2018 > > "}}, {"value":"beeline", "attributes":{"Date": "Mon Jul 16 > 07:11:59 2018 > > "}}, {"value":"megafon", "attributes":{"Date": "Mon Jul 16 > 07:11:59 2018 > > "}}, {"value":"megafon", "attributes":{"Date": "Mon Jul 16 > 07:12:54 2018 > > "}}, {"value":"mts", "attributes":{"Date": "Mon Jul 16 07:12:54 > 2018 > > "}}, {"value":"mts", "attributes":{"Date": "Mon Jul 16 07:13:51 > 2018 > > "}}, {"value":"beeline", "attributes":{"Date": "Mon Jul 16 > 07:13:52 2018 > > "}}]} > > > > This is incorrect, because it shoulde not include "\n" symbols. > > > > > > _______________________________________________ > > Users mailing list > > Users@lists.opensips.org > > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > > -- > Răzvan Crainea > OpenSIPS Core Developer > http://www.opensips-solutions.com > > _______________________________________________ > Users mailing list > Users@lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > Users mailing list > Users@lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > ------------------------------ > > End of Users Digest, Vol 120, Issue 29 > ************************************** >
_______________________________________________ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users