Problem/Motivation

If this tool is used in web solutions, where code is hosted in such infrastructure where SSL certificates do not matter/are misconfigured for some reason, it should still be possible to clear caches without hitting SSL verification error.
For example, if project is being deployed via CI/CD solution and host machine where the pipeline runs is under the reverse proxy and does not care about SSL certificates, at the moment it would error out and halt the pipeline or any automatic deployment tool if additional checks in pipeline are not added.

Proposed resolution

Add additional option to set CURL options to ignore SSL verification when performing request.

Issue fork cache_utility-3267463

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

irmantasp created an issue. See original summary.

irmantasp opened merge request !1

toamit’s picture

toamit commented

This is already supported, you can uncheck the following option on the module configuration page /admin/config/development/cache_utility
[ ] Force curl and drush commands to show urls with https, instead of http

irmantasp’s picture

irmantasp commented

This is actually not the case. And that does not apply here.
Exact case is:

Webserver is configured like this:
All traffic goes through HTTPS, there is webserver configuration, which does redirect from HTTP to HTTPS. It has internal certificates, which when calling from pipeline/inside server resolve as invalid.

Proxy is configured to resolve SSL certificate properly and redirect traffic to webserver via HTTPS or HTTP, webserver resolves it internally.
And this is were that checkbox does not work, as simply HTTP is redirected to HTTP and since certificate is internal/selfsigned it fails verification.

Adding option to completely ignore SSL verification completely resolves the issue if similar case would be encountered.

thecooltechguy’s picture

thecooltechguy commented

Hi irmantasp,

Thanks for reporting this issue.

We've just released a new version (1.0.1) containing a fix for this, extending your proposed solution.

thecooltechguy’s picture

thecooltechguy commented
Version: 1.0.0 » 1.0.1
Status: Active » Fixed

This issue has been resolved (version 1.01).

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.