CurlMethodOptionOrderConflict

warning native on by default

Group: Probable bugs

cURL method options can override previously selected request modes. Configure one consistent final method before executing the transfer.

Example

<?php
$h=curl_init();curl_setopt($h,CURLOPT_POST,true);curl_setopt($h,CURLOPT_HTTPGET,true);curl_exec($h);
$g=curl_init();curl_setopt($g,CURLOPT_HTTPGET,true);curl_setopt($g,CURLOPT_POST,true);curl_exec($g);

Reported:

• line 2: Configure a consistent final HTTP request method.
• line 3: Configure a consistent final HTTP request method.

Detection

• Same curl handle sets CURLOPT_POST=true then CURLOPT_HTTPGET=true before one curl_exec, or vice versa, without intervening execution. Highlight later option; definite opposing mode values only.
• Resolve builtin functions, classes, constants and methods; user-defined lookalikes are excluded. Follow only bounded local proof in one lexical scope.
• Emit one finding per violating operation, not per supporting evidence statement. When the proof is inconclusive, nothing is reported.

Exceptions (no report)

• Do not report unresolved or shadowed builtin names, unknown values, or incomplete receiver/type provenance. Unknown calls, aliases escaping, and intervening writes invalidate local proof. Similar code outside the stated detection contract is not a finding.
• Both standard suppression forms suppress this native ID.

Fix

None. Choosing a repair requires intent or additional runtime information.

PHP versions

Available throughout supported PHP 5.3–8.5 where the referenced builtin/extension is available. Respect syntax/version-specific receiver contracts; unavailable APIs are not this rule’s concern.

Configure

In custos.json:

{
  "rules": {
    "CurlMethodOptionOrderConflict": {
      "enabled": false
    }
  }
}

Suppress

Before the statement or declaration (or the first statement of the file):

// @custos-ignore CurlMethodOptionOrderConflict