But it no longer passes through a method of PURGE, so the whole thing fails. I can't see how to properly use a custom method with the new system. It defaults to a GET now which ... not what I wanted.
GET /
GET /feed/
GET /2016/07/dsafdsaf/
GET /feed/rdf/
GET /feed/rss/
GET /feed/
GET /feed/
GET /feed/atom/
GET /comments/feed/
GET /2016/07/dsafdsaf/feed/
Those should all be PURGE and not GET.
Similarly, when I do a full flush, I get this: GET /.*
I've reached out to @rmccue and @ocean90 via WP Slack.
I'm having a weird issue with the new requests WP_Http API. I usually run this:
$response = wp_remote_request($purgeme, array('method' => 'PURGE', 'headers' => array( 'host' => $p['host'], 'X-Purge-Method' => $varnish_x_purgemethod ) ) );
But it no longer passes through a method of PURGE, so the whole thing fails. I can't see how to properly use a custom method with the new system. It defaults to a GET now which ... not what I wanted.
Those should all be PURGE and not GET.
Similarly, when I do a full flush, I get this:
GET /.*
I've reached out to @rmccue and @ocean90 via WP Slack.