Resolving Form POST Errors & AJAX Endpoint Routing
Diagnose and resolve form POST errors, CORS preflight blocks, and ensure contact leads are delivered reliably on edge-accelerated sites.
Troubleshooting Form Errors
On Nimbica edge-accelerated sites, page HTML is served from the edge — but form submissions still route dynamically to your WordPress origin server. If contact forms return 403, 404, or "CORS preflight request blocked" in the browser console, the form action URL or proxy handler requires adjustment.
Checklist for Reliable Form Submissions
- Ensure the form uses AJAX submission mode rather than direct synchronous POST redirects.
- Verify that your origin server permits incoming REST API requests from Nimbica edge workers.
- Ensure reCAPTCHA / Cloudflare Turnstile keys are authorized for both your custom domain and origin domain.
- Confirm
/wp-json/*,/cart, and form action endpoints are listed in Dynamic Path Exclusions in your Nimbica plugin settings so they are never served statically.
📋 Verified Execution Steps (3 Total Steps)
In WP-Admin ➔ Nimbica ➔ Settings, confirm that your form endpoint (e.g., /wp-json/contact-form-7/v1/contact) is listed in Dynamic Path Exclusions.
Open the Network tab, submit the form, and verify that the AJAX endpoint returns HTTP 200 with JSON payload.
If using Akismet, Wordfence, or reCAPTCHA, ensure edge proxy requests are whitelisted.