Searched refs:valid (Results 1 – 10 of 10) sorted by relevance
19 nxt_bool_t valid; in nxt_mp_test() local36 valid = nxt_mp_test_sizes(cluster_size, page_alignment, page_size, in nxt_mp_test()38 if (!valid) { in nxt_mp_test()
37 xmllint --noout --valid changes.xml48 xmllint --noout --valid changes.xml59 xmllint --noout --valid changes.xml
4398 detail: 'A valid JSON value is expected here. It must be either a
31 uriTemplate.invalidPath=The path [{0}] is not valid.32 uriTemplate.invalidSegment=The segment [{0}] is not valid in the provided path [{1}]
353 nxt_bool_t valid; in nxt_mp_test_sizes() local357 valid = nxt_expect(1, (nxt_is_power_of_two(page_alignment) in nxt_mp_test_sizes()360 if (!valid) { in nxt_mp_test_sizes()366 valid = nxt_expect(1, (page_size >= 64 in nxt_mp_test_sizes()373 if (!valid) { in nxt_mp_test_sizes()
192 # 1506-159 (E) Bit field type specified for XXX is not valid.
71 wsFrame.oneByteCloseCode=The client sent a close frame with a single byte payload which is not valid80 wsHandshakeRequest.invalidUri=The string [{0}] cannot be used to construct a valid URI
465 *) Change: any characters valid according to RFC 7230 are now allowed in488 discarding request header fields with irregular (but still valid)
241 necessary to make such provision valid and enforceable.