Before this update, when tls.insecureSkipVerify: true was defined alongside type: http and not secure URL in the Cluster Log Forwarder configuration, the certificate validation was not skipped as intended. This misconfiguration led to the collector failing because it attempted to validate certificates despite the setting. With this update, we've added additional validation for the URL scheme. Now, if tls.insecureSkipVerify: true is set but the URL is not secure (i.e., does not use HTTPS), a misconfiguration error is raised, thus preventing potential security issues and ensuring the configuration behaves as expected.