Woocommerce Connection error using plesk and modsecurity

1. Create a wordpress site on plesk panel, install Jetpack and Woocommerce plugin
2. Enable modsecurity with COMODO WAF rules
3. Connect Woocommerce with phone app
4. Connection error
--

#### What I expected

Successful connection:
GET /?rest_route=%2F&_method=get&_fields=authentication%2Cnamespaces&_for=jetpack&token=xxx_token_xxx%25r%24%3A1%3A1×tamp=1604325546&nonce=AZAMkCnmTD&body-hash&signature=xxx_signature_xxx%3D HTTP/1.0

#### What happened instead
Could not load the content ERROR: (Apache error)

(20014)Internal error (specific information not available): AH01075: Error dispatching request to : (passing brigade to output filters), referer: https://*******.com/?rest_route=%2Fwc-analytics%2Fleaderboards&_method=get&after=2020-11-02T00%3A00%3A00&before=2020-11-08T23%3A59%3A59&per_page=3&interval=week&_for=jetpack&token=xxx_token_xxx%3A1%3A1×tamp=1604327267&nonce=pCW1teoAgG&body-hash&signature=xxx_signature_xxx%3D

[client 192.0.100.17] ModSecurity: Access denied with code 403 (phase 3). Match of "validateByteRange 0-31" against "ARGS:body-hash" required. [file "/etc/apache2/modsecurity.d/rules/comodo_free/30_Apps_OtherApps.conf"] [line "6649"] [id "243420"] [rev "4"] [msg "COMODO WAF: Information disclosure vulnerability in Eclipse Jetty before 9.2.9.v20150224 (CVE-2015-2080)\|\|*******.com\|F\|2"] [severity "CRITICAL"] [tag "CWAF"] [tag "OtherApps"] [hostname "*******.com"] [uri "/index.php"] [unique_id "X6AXZakRmg-xVsR4cUY9@gAAAFE"], referer: https://*******.com/?rest_route=%2Fwc-analytics%2Fleaderboards&_method=get&after=2020-11-02T00%3A00%3A00&per_page=3&before=2020-11-02T23%3A59%3A59&interval=day&_for=jetpack&token=xxx_token_xxx%3A1×tamp=1604327267&nonce=VcMfpUemS5&body-hash&signature=xxx_signature_xxx%3D

--

**Screenshots**
If applicable, add screenshots to help explain your problem.

Start by reproducing the WooCommerce phone-app connection through /index.php with Plesk, Apache, and the COMODO ModSecurity rules enabled. Read the Apache error and ModSecurity rule details for rule 243420, then compare the blocked body-hash request with a successful request; done means identifying a supported configuration or documenting the remaining incompatibility.

Written by the indexing model from the issue text.