Hi.

If scheme selected https the following error occurred. (even if uncheck the "Verify SSL certificate")

Error Message:
item failed due InvalidArgumentException

I checked api host server logs, it seems that it does not send http request to api host server.

The full setting is below:

Hostname: xxxxx.com
Port: 443
Path:/
Request Method:POST
Scheme:HTTPS
*uncheck Treat 4XX and 5XX responses as a failed invalidation.

I don't know where are the mistake.

CommentFileSizeAuthor
#9 2892552-verify-option-scheme-update-6.patch569 bytesvidorado
#8 2892552-verify-option-scheme-update-6.patch705 bytesvidorado
#6 2892552-verify-option-scheme-update-6.patch737 bytesvidorado
#3 2892552-verify-option-scheme-update.patch414 bytesbrooksbrown

Issue fork purge_purger_http-2892552

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

redboxhosting created an issue. See original summary.

mrsimonelliott’s picture

mrsimonelliott commented

I confirm this issue.

Even with "Verify SSL" unchecked I get an error.

purger_http_2832d7e853: item failed due InvalidArgumentException, details (JSON): {"msg":"SSL CA bundle not found: [error]
0","uri":"https:\/\/xx.xx.xx.xx:443\/node\/226","method":"PURGE","guzzle_opt":{"http_errors":true,"connect_timeout":1,"timeout":1,"verify":"0"},"headers":{"user-agent":"purge_purger_http module for Drupal
8.","x-acquia-purge":"xxxxxxstg","accept-encoding":"gzip","host":"xxxxxxstg.prod.acquia-sites.com"}}

Alter config back to http on port 80 and all is good.

brooksbrown’s picture

brooksbrown commented
StatusFileSize
new 2892552-verify-option-scheme-update.patch414 bytes

I believe I've narrowed down this issue to the guzzle verify option being set as "0" rather than false. I'm attaching a patch that updates the schema for this (you will need to re-save the purger's configurations to test).

zerolab’s picture

zerolab commented
Status: Active » Needs review
floretan’s picture

floretan commented

I applied the patch and updated the configuration, I can confirm that this works. To make this patch complete, we should probably update the configuration using an update hook.

vidorado’s picture

vidorado commented
StatusFileSize
new 2892552-verify-option-scheme-update-6.patch737 bytes

Hi,

This is another solution less "pure", but it doesn't require updating the database schema.

Status: Needs review » Needs work

The last submitted patch, 6: 2892552-verify-option-scheme-update-6.patch, failed testing. View results

vidorado’s picture

vidorado commented
StatusFileSize
new 2892552-verify-option-scheme-update-6.patch705 bytes

Oops, a mistake in the patch

vidorado’s picture

vidorado commented
StatusFileSize
new 2892552-verify-option-scheme-update-6.patch569 bytes

Another try to get the patch passing tests

vidorado’s picture

vidorado commented
Status: Needs work » Needs review
iaugur’s picture

iaugur commented

#9 patch works for me and corrects the issue - Thanks

jonhattan’s picture

jonhattan
Primary language Spanish
Location Plasencia
commented
Version: 8.x-1.0-beta4 » 8.x-1.x-dev
Assigned: redboxhosting » Unassigned
Priority: Normal » Major
Status: Needs review » Reviewed & tested by the community
Issue tags: -https

Both #3 and #9 works.

cesarmiquel’s picture

cesarmiquel commented

I saw this same issue and #9 fixes it. Looks good to me!

ezra’s picture

ezra commented

#9 worked for me as well.

DieterHolvoet made their first commit to this issue’s fork.

DieterHolvoet opened merge request !3

dieterholvoet’s picture

dieterholvoet commented
Status: Reviewed & tested by the community » Fixed

I went for the cleanest solution, changing the config schema, and I added an update hook to update existing values.

  • DieterHolvoet committed 95cdcb05 on 8.x-1.x 
    Issue #2892552 by vidorado, DieterHolvoet, brooksbrown: scheme is https...

Status: Fixed » Closed (fixed)

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