After configuring a new HTTP purger (bundled or not), and pointing it at Varnish running on 127.0.0.1, port 81, I ran drush p-queue-work, and got a bunch of the following errors:

GuzzleHttp\Exception\ClientException thrown by 596e2dc568, invalidation marked as failed. URI:                   [error]
http://127.0.0.1/# METHOD: BAN# HEADERS:   ["user-agent"]=>,  S(38) "purge_purger_http module for Drupal 8.",
  ["x-drupal-cache-tags"]=>,  S(23) "config:system.menu.main", }#mOPT:   ["http_errors"]=>,  B(true),  
["connect_timeout"]=>,  F(1),   ["timeout"]=>,  F(1), }#MSG: Client error: 405#

Looking through them, I noticed my port wasn't being added to the URI passed into Guzzle. I'll attach a patch that makes sure the port is added (in addition to schema, host, and path).

CommentFileSizeAuthor
#2 guzzle_clientexception-2691913-2.patch617 bytesgeerlingguy
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

geerlingguy created an issue. See original summary.

geerlingguy’s picture

geerlingguy CreditAttribution: geerlingguy as a volunteer and at Acquia commented
Status: Active » Needs review
FileSize
guzzle_clientexception-2691913-2.patch617 bytes

Patch attached.

nielsvm’s picture

nielsvm CreditAttribution: nielsvm as a volunteer and at Acquia commented
Status: Needs review » Closed (fixed)

Thank you!

[8.x-1.x 9cc504f] Issue #2691913 by geerlingguy: Guzzle ClientException when HTTP purge is not on port 80
 Author: geerlingguy <geerlingguy@389011.no-reply.drupal.org>
 1 file changed, 2 insertions(+), 1 deletion(-)

This will end up as 8.x-1.0-beta2 later today, probably <2 hours from this message.