WooCommerce REST API per_page limit inconsistent between local and production

WooCommerce REST API product list requests using per_page greater than 100 return more than 100 items on a local development instance, while the same request in production appears capped at 100 items. The documented maximum is 100 per page, but enforcement is not consistent across environments.

Goal: determine whether the difference originates from WooCommerce core pagination logic, server configuration, caching layers, or CDN plugins that normalize response headers such as X-WP-TotalPages.

Assumptions: WooCommerce 7.x or newer, standard /wp-json/wc/v3/products endpoint, no custom REST route overrides. Behavior may differ by release and by active plugins that modify REST responses.

Raw header comparison across environments is required to confirm whether the cap is applied consistently.

• Does WooCommerce core enforce the per_page maximum of 100 regardless of server environment?
• Can caching or CDN plugins cause local responses to exceed the documented limit while production responses remain capped?
• Should the X-WP-TotalPages header be trusted when per_page exceeds 100?