blocks|key|1284939|text|是的，完全的正则表达式验证是可能的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1284940|大多数现代regex实现都允许使用递归regexpression，这可以验证完整的JSON序列化结构。json.org+specification让这一切变得非常简单。|offset|length|1284941|$pcre_regex+=+'
++/
++(?(DEFINE)
+++++(?<number>+++-?+(?=+[1-9]%7C0(?!\d)+)+\d%2B+(\.\d%2B)?+([eE]+[%2B-]?+\d%2B)?+)++++
+++++(?<boolean>+++true+%7C+false+%7C+null+)
+++++(?<string>++++"+([%5E"\\\\]*+%7C+\\\\+["\\\\bfnrt\/]+%7C+\\\\+u+[0-9a-f]{4}+)*+"+)
+++++(?<array>+++++\[++(?:++(?&json)++(?:+,+(?&json)++)*++)?++\s*+\]+)
+++++(?<pair>++++++\s*+(?&string)+\s*+:+(?&json)++)
+++++(?<object>++++\{++(?:++(?&pair)++(?:+,+(?&pair)++)*++)?++\s*+\}+)
+++++(?<json>+++\s*+(?:+(?&number)+%7C+(?&boolean)+%7C+(?&string)+%7C+(?&array)+%7C+(?&object)+)+\s*+)
++)
++\A+(?&json)+\Z
++/six+++
';|code-block|syntax|javascript|1284942|它在PHP中和PCRE+functions+一起工作得很好。不需要修改就可以在Perl中工作；当然也可以适用于其他语言。此外，它还成功地使用了JSON+test+cases。|1284943|更简单的RFC4627验证|1284944|一种更简单的方法是RFC4627,+section+6中指定的最小一致性检查。然而，它只是作为安全测试和基本的无效预防措施：|1284945|++var+my_JSON_object+=+!(/[%5E,:{}\[\]0-9.\-%2BEaeflnr-u+\n\r\t]/.test(
+++++++++text.replace(/"(\\.%7C[%5E"\\])*"/g,+'')))+&&
+++++eval('('+%2B+text+%2B+')');|1284946|entityMap|0|LINK|mutability|MUTABLE|url|http://json.org/|1|http://php.net/preg_match|2|http://www.json.org/JSON_checker/test/pass1.json|3|https://datatracker.ietf.org/doc/html/rfc4627#section-6^0|0|1F|M|0|0|0|7|F|1|1Z|F|2|0|0|9|I|3|0|0^^$0|@$1|2|3|4|5|6|7|16|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|17|8|@]|9|@$D|18|E|19|1|1A]]|A|$]]|$1|F|3|G|5|H|7|1B|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|1C|8|@]|9|@$D|1D|E|1E|1|1F]|$D|1G|E|1H|1|1I]]|A|$]]|$1|M|3|N|5|6|7|1J|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|1K|8|@]|9|@$D|1L|E|1M|1|1N]]|A|$]]|$1|Q|3|R|5|H|7|1O|8|@]|9|@]|A|$I|J]]|$1|S|3|-4|5|6|7|1P|8|@]|9|@]|A|$]]]|T|$U|$5|V|W|X|A|$Y|Z]]|10|$5|V|W|X|A|$Y|11]]|12|$5|V|W|X|A|$Y|13]]|14|$5|V|W|X|A|$Y|15]]]]

<h2>Yes, a complete regex validation is possible.</h2>
Most modern regex implementations allow for recursive regexpressions, which can verify a complete JSON serialized structure. The <a href="http://json.org/" rel="nofollow noreferrer">json.org specification</a> makes it quite straightforward.
<pre><code>$pcre_regex = '
 /
 (?(DEFINE)
 (?&lt;number&gt; -? (?= [1-9]|0(?!\d) ) \d+ (\.\d+)? ([eE] [+-]? \d+)? ) 
 (?&lt;boolean&gt; true | false | null )
 (?&lt;string&gt; &quot; ([^&quot;\\\\]* | \\\\ [&quot;\\\\bfnrt\/] | \\\\ u [0-9a-f]{4} )* &quot; )
 (?&lt;array&gt; \[ (?: (?&amp;json) (?: , (?&amp;json) )* )? \s* \] )
 (?&lt;pair&gt; \s* (?&amp;string) \s* : (?&amp;json) )
 (?&lt;object&gt; \{ (?: (?&amp;pair) (?: , (?&amp;pair) )* )? \s* \} )
 (?&lt;json&gt; \s* (?: (?&amp;number) | (?&amp;boolean) | (?&amp;string) | (?&amp;array) | (?&amp;object) ) \s* )
 )
 \A (?&amp;json) \Z
 /six 
';
</code></pre>
It works quite well in PHP with the <a href="http://php.net/preg_match" rel="nofollow noreferrer">PCRE functions </a>. Should work unmodified in Perl; and can certainly be adapted for other languages. Also it succeeds with the <a href="http://www.json.org/JSON_checker/test/pass1.json" rel="nofollow noreferrer">JSON test cases</a>.
<h3>Simpler RFC4627 verification</h3>
A simpler approach is the minimal consistency check as specified in <a href="https://datatracker.ietf.org/doc/html/rfc4627#section-6" rel="nofollow noreferrer">RFC4627, section 6</a>. It's however just intended as security test and basic non-validity precaution:
<pre><code> var my_JSON_object = !(/[^,:{}\[\]0-9.\-+Eaeflnr-u \n\r\t]/.test(
 text.replace(/&quot;(\\.|[^&quot;\\])*&quot;/g, ''))) &amp;&amp;
 eval('(' + text + ')');
</code></pre>

blocks|key|1284992|text|对于“字符串和数字”，我认为数字的部分正则表达式：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1284993|-?(?:0%7C[1-9]\d*)(?:\.\d%2B)(?:[eE][%2B-]\d%2B)?|code-block|syntax|javascript|1284994|应该改为：|1284995|-?(?:0%7C[1-9]\d*)(?:\.\d%2B)?(?:[eE][%2B\-]?\d%2B)?|1284996|因为数字的小数部分是可选的，而且在[%2B-]中转义-符号可能更安全，因为它在括号之间有特殊的含义|offset|length|style|CODE|1284997|entityMap^0|0|0|0|0|H|4|O|1|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|U|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|W|8|@$M|X|N|Y|O|P]|$M|Z|N|10|O|P]]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|R|$]]

For "strings and numbers", I think that the partial regular expression for numbers:

<pre><code>-?(?:0|[1-9]\d*)(?:\.\d+)(?:[eE][+-]\d+)?
</code></pre>

should be instead:

<pre><code>-?(?:0|[1-9]\d*)(?:\.\d+)?(?:[eE][+\-]?\d+)?
</code></pre>

since the decimal part of the number is optional, and also it is probably safer to escape the <code>-</code> symbol in <code>[+-]</code> since it has a special meaning between brackets

blocks|key|1285048|text|我创建了一个Mario解决方案的Ruby实现，它确实有效：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1285049|#+encoding:+utf-8

module+Constants
++JSON_VALIDATOR_RE+=+/(
+++++++++#+define+subtypes+and+build+up+the+json+syntax,+BNF-grammar-style
+++++++++#+The+{0}+is+a+hack+to+simply+define+them+as+named+groups+here+but+not+match+on+them+yet
+++++++++#+I+added+some+atomic+grouping+to+prevent+catastrophic+backtracking+on+invalid+inputs
+++++++++(?<number>++-?(?=[1-9]%7C0(?!\d))\d%2B(\.\d%2B)?([eE][%2B-]?\d%2B)?){0}
+++++++++(?<boolean>+true+%7C+false+%7C+null+){0}
+++++++++(?<string>++"+(?>[%5E"\\\\]*+%7C+\\\\+["\\\\bfnrt\/]+%7C+\\\\+u+[0-9a-f]{4}+)*+"+){0}
+++++++++(?<array>+++\[+(?>+\g<json>+(?:+,+\g<json>+)*+)?+\s*+\]+){0}
+++++++++(?<pair>++++\s*+\g<string>+\s*+:+\g<json>+){0}
+++++++++(?<object>++\{+(?>+\g<pair>+(?:+,+\g<pair>+)*+)?+\s*+\}+){0}
+++++++++(?<json>++++\s*+(?>+\g<number>+%7C+\g<boolean>+%7C+\g<string>+%7C+\g<array>+%7C+\g<object>+)+\s*+){0}
+++++++)
++++\A+\g<json>+\Z
++++/uix
end

##########+inline+test+running
if+__FILE__==$PROGRAM_NAME

++#+support
++class+String
++++def+unindent
++++++gsub(/%5E#{scan(/%5E(?!\n)\s*/).min_by{%7Cl%7Cl.length}}/u,+"")
++++end
++end

++require+'test/unit'+unless+defined?+Test::Unit
++class+JsonValidationTest+<+Test::Unit::TestCase
++++include+Constants

++++def+setup

++++end

++++def+test_json_validator_simple_string
++++++assert_not_nil+%25s[+{"somedata":+5+}].match(JSON_VALIDATOR_RE)
++++end

++++def+test_json_validator_deep_string
++++++long_json+=+<<-JSON.unindent
++++++{
++++++++++"glossary":+{
++++++++++++++"title":+"example+glossary",
++++++++++"GlossDiv":+{
++++++++++++++++++"id":+1918723,
++++++++++++++++++"boolean":+true,
++++++++++++++++++"title":+"S",
++++++++++++"GlossList":+{
++++++++++++++++++++++"GlossEntry":+{
++++++++++++++++++++++++++"ID":+"SGML",
++++++++++++++++"SortAs":+"SGML",
++++++++++++++++"GlossTerm":+"Standard+Generalized+Markup+Language",
++++++++++++++++"Acronym":+"SGML",
++++++++++++++++"Abbrev":+"ISO+8879:1986",
++++++++++++++++"GlossDef":+{
++++++++++++++++++++++++++++++"para":+"A+meta-markup+language,+used+to+create+markup+languages+such+as+DocBook.",
++++++++++++++++++"GlossSeeAlso":+["GML",+"XML"]
++++++++++++++++++++++++++},
++++++++++++++++"GlossSee":+"markup"
++++++++++++++++++++++}
++++++++++++++++++}
++++++++++++++}
++++++++++}
++++++}
++++++JSON

++++++assert_not_nil+long_json.match(JSON_VALIDATOR_RE)
++++end

++end
end|code-block|syntax|javascript|1285050|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

I created a Ruby implementation of Mario's solution, which does work:

<pre><code># encoding: utf-8

module Constants
 JSON_VALIDATOR_RE = /(
 # define subtypes and build up the json syntax, BNF-grammar-style
 # The {0} is a hack to simply define them as named groups here but not match on them yet
 # I added some atomic grouping to prevent catastrophic backtracking on invalid inputs
 (?&lt;number&gt; -?(?=[1-9]|0(?!\d))\d+(\.\d+)?([eE][+-]?\d+)?){0}
 (?&lt;boolean&gt; true | false | null ){0}
 (?&lt;string&gt; " (?&gt;[^"\\\\]* | \\\\ ["\\\\bfnrt\/] | \\\\ u [0-9a-f]{4} )* " ){0}
 (?&lt;array&gt; \[ (?&gt; \g&lt;json&gt; (?: , \g&lt;json&gt; )* )? \s* \] ){0}
 (?&lt;pair&gt; \s* \g&lt;string&gt; \s* : \g&lt;json&gt; ){0}
 (?&lt;object&gt; \{ (?&gt; \g&lt;pair&gt; (?: , \g&lt;pair&gt; )* )? \s* \} ){0}
 (?&lt;json&gt; \s* (?&gt; \g&lt;number&gt; | \g&lt;boolean&gt; | \g&lt;string&gt; | \g&lt;array&gt; | \g&lt;object&gt; ) \s* ){0}
 )
 \A \g&lt;json&gt; \Z
 /uix
end

########## inline test running
if __FILE__==$PROGRAM_NAME

 # support
 class String
 def unindent
 gsub(/^#{scan(/^(?!\n)\s*/).min_by{|l|l.length}}/u, "")
 end
 end

 require 'test/unit' unless defined? Test::Unit
 class JsonValidationTest &lt; Test::Unit::TestCase
 include Constants

 def setup

 end

 def test_json_validator_simple_string
 assert_not_nil %s[ {"somedata": 5 }].match(JSON_VALIDATOR_RE)
 end

 def test_json_validator_deep_string
 long_json = &lt;&lt;-JSON.unindent
 {
 "glossary": {
 "title": "example glossary",
 "GlossDiv": {
 "id": 1918723,
 "boolean": true,
 "title": "S",
 "GlossList": {
 "GlossEntry": {
 "ID": "SGML",
 "SortAs": "SGML",
 "GlossTerm": "Standard Generalized Markup Language",
 "Acronym": "SGML",
 "Abbrev": "ISO 8879:1986",
 "GlossDef": {
 "para": "A meta-markup language, used to create markup languages such as DocBook.",
 "GlossSeeAlso": ["GML", "XML"]
 },
 "GlossSee": "markup"
 }
 }
 }
 }
 }
 JSON

 assert_not_nil long_json.match(JSON_VALIDATOR_RE)
 end

 end
end
</code></pre>

blocks|key|1070496|text|JSON数组中的尾随逗号导致Perl5.16挂起，可能是因为它一直在回溯。我不得不添加一个回溯终止指令：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1070497|(?<json>+++\s*+(?:+(?&number)+%7C+(?&boolean)+%7C+(?&string)+%7C+(?&array)+%7C+(?&object)+)(*PRUNE)+\s*+)
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++%5E%5E%5E%5E%5E%5E%5E%5E|code-block|syntax|javascript|1070498|这样，一旦它识别出一个不是“可选”的构造(*或?)，它就不应该试图在它上面回溯，试图将它识别为其他东西。|offset|length|style|CODE|1070499|entityMap^0|0|0|L|1|N|1|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@$I|R|J|S|K|L]|$I|T|J|U|K|L]]|9|@]|A|$]]|$1|M|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|N|$]]

A trailing comma in a JSON array caused my Perl 5.16 to hang, possibly because it kept backtracking. I had to add a backtrack-terminating directive:

<pre><code>(?&lt;json&gt; \s* (?: (?&amp;number) | (?&amp;boolean) | (?&amp;string) | (?&amp;array) | (?&amp;object) )(*PRUNE) \s* )
 ^^^^^^^^
</code></pre>

This way, once it identifies a construct that is not 'optional' (<code>*</code> or <code>?</code>), it shouldn't try backtracking over it to try to identify it as something else.

blocks|key|1070527|text|下面是我的验证字符串的regexp：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1070528|%5E\"([%5E\"\\]*%7C\\(["\\\/bfnrt]{1}%7Cu[a-f0-9]{4}))*\"$|code-block|syntax|javascript|1070529|是用original+syntax+diagramm写的。|offset|length|1070530|entityMap|0|LINK|mutability|MUTABLE|url|http://www.json.org/^0|0|0|2|O|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|U|8|@]|9|@$I|V|J|W|1|X]]|A|$]]|$1|K|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|L|$M|$5|N|O|P|A|$Q|R]]]]

Here my regexp for validate string:

<pre><code>^\"([^\"\\]*|\\(["\\\/bfnrt]{1}|u[a-f0-9]{4}))*\"$
</code></pre>

Was written usign <a href="http://www.json.org/" rel="nofollow">original syntax diagramm</a>.

blocks|key|1070574|text|如上所述，如果您使用的语言附带了JSON-library，那么可以使用它来尝试解码字符串，并在失败时捕获异常/错误！如果该语言不支持(FreeMarker就有这种情况)，下面的正则表达式至少可以提供一些非常基本的验证(它是为PCRE编写的，以便更多用户可以测试/使用)。它不像公认的解决方案那样万无一失，但也不那么可怕。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1070575|~%5E\{\s*\".*\}$%7C%5E\[\n?\{\s*\".*\}\n?\]$~s|code-block|syntax|javascript|1070576|简短的解释：|1070577|//+we+have+two+possibilities+in+case+the+string+is+JSON
//+1.+the+string+passed+is+"just"+a+JSON+object,+e.g.+{"item":+[],+"anotheritem":+"content"}
//+this+can+be+matched+by+the+following+regex+which+makes+sure+there+is+at+least+a+{"+at+the
//+beginning+of+the+string+and+a+}+at+the+end+of+the+string,+whatever+is+inbetween+is+not+checked!

%5E\{\s*\".*\}$

//+OR+(character+"%7C"+in+the+regex+pattern)
//+2.+the+string+passed+is+a+JSON+array,+e.g.+[{"item":+"value"},+{"item":+"value"}]
//+which+would+be+matched+by+the+second+part+of+the+pattern+above

%5E\[\n?\{\s*\".*\}\n?\]$

//+the+s+modifier+is+used+to+make+"."+also+match+newline+characters+(can+happen+in+prettyfied+JSON)|1070578|如果我无意中错过了一些可能会破坏这一点的东西，我很感谢大家的评论！|1070579|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|S|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

As was written above, if the language you use has a JSON-library coming with it, use it to try decoding the string and catch the exception/error if it fails! If the language does not (just had such a case with FreeMarker) the following regex could at least provide some very basic validation (it's written for PHP/PCRE to be testable/usable for more users). It's not as foolproof as the accepted solution, but also not that scary =):

<pre><code>~^\{\s*\".*\}$|^\[\n?\{\s*\".*\}\n?\]$~s
</code></pre>

short explanation:

<pre><code>// we have two possibilities in case the string is JSON
// 1. the string passed is "just" a JSON object, e.g. {"item": [], "anotheritem": "content"}
// this can be matched by the following regex which makes sure there is at least a {" at the
// beginning of the string and a } at the end of the string, whatever is inbetween is not checked!

^\{\s*\".*\}$

// OR (character "|" in the regex pattern)
// 2. the string passed is a JSON array, e.g. [{"item": "value"}, {"item": "value"}]
// which would be matched by the second part of the pattern above

^\[\n?\{\s*\".*\}\n?\]$

// the s modifier is used to make "." also match newline characters (can happen in prettyfied JSON)
</code></pre>

if I missed something that would break this unintentionally, I'm grateful for comments!

blocks|key|1070602|text|我意识到这是6年前的事了。然而，我认为有一种解决方案，这里没有人提到，它比regexing容易得多。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1070603|function+isAJSON(string)+{
++++try+{
++++++++JSON.parse(string)++
++++}+catch(e)+{
++++++++if(e+instanceof+SyntaxError)+return+false;
++++};++
++++return+true;
}|code-block|syntax|javascript|1070604|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

I realize that this is from over 6 years ago. However, I think there is a solution that nobody here has mentioned that is way easier than regexing 

<pre><code>function isAJSON(string) {
 try {
 JSON.parse(string) 
 } catch(e) {
 if(e instanceof SyntaxError) return false;
 }; 
 return true;
}
</code></pre>

blocks|key|1070655|text|我尝试了@mario的答案，但它对我不起作用，因为我已经从JSON.org+(archive)下载了测试套件，并且有4个失败的测试(fail1.json，fail18.json，fail25.json，fail27.json)。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1070656|我调查了错误，发现fail1.json实际上是正确的(根据手册的note和RFC-7159，有效字符串也是一个有效的JSON)。文件fail18.json也不是这样的，因为它实际上包含了正确的深度嵌套的JSON：|style|CODE|1070657|[[[[[[[[[[[[[[[[[[[["Too+deep"]]]]]]]]]]]]]]]]]]]]|code-block|syntax|javascript|1070658|所以只剩下两个文件：fail25.json和fail27.json|1070659|["++tab+character+++in++string++"]|1070660|和|1070661|["line
break"]|1070662|两者都包含无效字符。所以我像这样更新了模式(字符串子模式更新)：|1070663|$pcreRegex+=+'/
++++++++++(?(DEFINE)
+++++++++++++(?<number>+++-?+(?=+[1-9]%7C0(?!\d)+)+\d%2B+(\.\d%2B)?+([eE]+[%2B-]?+\d%2B)?+)
+++++++++++++(?<boolean>+++true+%7C+false+%7C+null+)
+++++++++++++(?<string>++++"+([%5E"\n\r\t\\\\]*+%7C+\\\\+["\\\\bfnrt\/]+%7C+\\\\+u+[0-9a-f]{4}+)*+"+)
+++++++++++++(?<array>+++++\[++(?:++(?&json)++(?:+,+(?&json)++)*++)?++\s*+\]+)
+++++++++++++(?<pair>++++++\s*+(?&string)+\s*+:+(?&json)++)
+++++++++++++(?<object>++++\{++(?:++(?&pair)++(?:+,+(?&pair)++)*++)?++\s*+\}+)
+++++++++++++(?<json>+++\s*+(?:+(?&number)+%7C+(?&boolean)+%7C+(?&string)+%7C+(?&array)+%7C+(?&object)+)+\s*+)
++++++++++)
++++++++++\A+(?&json)+\Z
++++++++++/six';|1070664|所以现在所有来自json.org的合法测试都可以通过了。|1070665|entityMap|0|LINK|mutability|MUTABLE|url|http://www.json.org/JSON_checker/test.zip|1|http://php.net/manual/en/function.json-decode.php|2|http://www.faqs.org/rfcs/rfc7159.html|3|http://www.json.org/^0|13|7|0|0|9|A|1U|B|W|4|1|11|8|2|0|0|A|B|M|B|0|0|0|0|0|0|8|8|3|0^^$0|@$1|2|3|4|5|6|7|1E|8|@]|9|@$A|1F|B|1G|1|1H]]|C|$]]|$1|D|3|E|5|6|7|1I|8|@$A|1J|B|1K|F|G]|$A|1L|B|1M|F|G]]|9|@$A|1N|B|1O|1|1P]|$A|1Q|B|1R|1|1S]]|C|$]]|$1|H|3|I|5|J|7|1T|8|@]|9|@]|C|$K|L]]|$1|M|3|N|5|6|7|1U|8|@$A|1V|B|1W|F|G]|$A|1X|B|1Y|F|G]]|9|@]|C|$]]|$1|O|3|P|5|J|7|1Z|8|@]|9|@]|C|$K|L]]|$1|Q|3|R|5|6|7|20|8|@]|9|@]|C|$]]|$1|S|3|T|5|J|7|21|8|@]|9|@]|C|$K|L]]|$1|U|3|V|5|6|7|22|8|@]|9|@]|C|$]]|$1|W|3|X|5|J|7|23|8|@]|9|@]|C|$K|L]]|$1|Y|3|Z|5|6|7|24|8|@]|9|@$A|25|B|26|1|27]]|C|$]]|$1|10|3|-4|5|6|7|28|8|@]|9|@]|C|$]]]|11|$12|$5|13|14|15|C|$16|17]]|18|$5|13|14|15|C|$16|19]]|1A|$5|13|14|15|C|$16|1B]]|1C|$5|13|14|15|C|$16|1D]]]]

I tried @mario's answer, but it didn't work for me, because I've downloaded test suite from JSON.org (<a href="http://www.json.org/JSON_checker/test.zip" rel="noreferrer">archive</a>) and there were 4 failed tests (fail1.json, fail18.json, fail25.json, fail27.json).

I've investigated the errors and found out, that <code>fail1.json</code> is actually correct (according to manual's <a href="http://php.net/manual/en/function.json-decode.php" rel="noreferrer">note</a> and <a href="http://www.faqs.org/rfcs/rfc7159.html" rel="noreferrer">RFC-7159</a> valid string is also a valid JSON). File <code>fail18.json</code> was not the case either, cause it contains actually correct deeply-nested JSON:

<pre><code>[[[[[[[[[[[[[[[[[[[["Too deep"]]]]]]]]]]]]]]]]]]]]
</code></pre>

So two files left: <code>fail25.json</code> and <code>fail27.json</code>:

<pre><code>[" tab character in string "]
</code></pre>

and

<pre><code>["line
break"]
</code></pre>

Both contains invalid characters. So I've updated the pattern like this (string subpattern updated):

<pre><code>$pcreRegex = '/
 (?(DEFINE)
 (?&lt;number&gt; -? (?= [1-9]|0(?!\d) ) \d+ (\.\d+)? ([eE] [+-]? \d+)? )
 (?&lt;boolean&gt; true | false | null )
 (?&lt;string&gt; " ([^"\n\r\t\\\\]* | \\\\ ["\\\\bfnrt\/] | \\\\ u [0-9a-f]{4} )* " )
 (?&lt;array&gt; \[ (?: (?&amp;json) (?: , (?&amp;json) )* )? \s* \] )
 (?&lt;pair&gt; \s* (?&amp;string) \s* : (?&amp;json) )
 (?&lt;object&gt; \{ (?: (?&amp;pair) (?: , (?&amp;pair) )* )? \s* \} )
 (?&lt;json&gt; \s* (?: (?&amp;number) | (?&amp;boolean) | (?&amp;string) | (?&amp;array) | (?&amp;object) ) \s* )
 )
 \A (?&amp;json) \Z
 /six';
</code></pre>

So now all legal tests from <a href="http://www.json.org" rel="noreferrer">json.org</a> can be passed.

I am looking for a Regex that allows me to validate json. 

I am very new to Regex's and i know enough that parsing with Regex is bad but can it be used to validate?

Regex to validate JSON

安全测试

JSON

Perl

我正在寻找一个允许我验证json的正则表达式。我是Regex的新手，我知道使用Regex进行解析很糟糕，但是它可以用来验证吗？

问正则表达式用于验证JSON
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问正则表达式用于验证JSONEN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问正则表达式用于验证JSON
EN