How to Fix "Mixed Content Blocked" Errors When Submitting Forms Over HTTPS?

Addressing Mixed Content Errors in HTTPS Pages: A Solution to "Mixed Content Blocked"

In an attempt to maintain a secure HTTPS connection, browsers often block requests for non-HTTPS resources from HTTPS pages. This can lead to errors such as "Mixed Content: The page at 'https://page.com' was loaded over HTTPS, but requested an insecure XMLHttpRequest endpoint 'http://XX.XXX.XX.XXX/vicidial/non_agent_api.php?queries=query=data'."

To resolve this mixed content issue in a scenario involving a form submission through GET and redirection to a thank-you page using AJAX, the following steps are recommended:

1. Analyze the Problem:

The root cause of the error lies in the fact that the form is being submitted to a non-HTTPS endpoint (HTTP). This creates a mixed content issue since the page is loaded over HTTPS.

2. Explore Solutions:

a. Convert the API to HTTPS: If possible, approach the API provider and request them to convert the endpoint to HTTPS. This eliminates the mixed content issue at the source.

b. Establish a PHP Proxy:

If converting the API to HTTPS is not feasible, you can utilize a PHP proxy. Create a PHP file on your server that receives the form data, forwards it to the HTTP API (using cURL), and then redirects the user to the thank-you page. This approach eliminates the mixed content error as the request is handled on the server-side, away from the browser's HTTPS context.

The above is the detailed content of How to Fix "Mixed Content Blocked" Errors When Submitting Forms Over HTTPS?. For more information, please follow other related articles on the PHP Chinese website!