deviantintegral/client_error_trace

A Drupal module to help track down HTTP 4XX client errors.

client_error_trace's Issues

Add a plugin to support checking node published status

This plugin should check the status property on a node, both from the database and from a cached node.

Project includes insecure guzzlehttp/guzzle as dependency

Note: The Drupal security team have made the determination that this issue can be fixed because there is no stable release of this project which is why this issue was created here.

As part of the httpoxy vulnerability, this module includes an affected version of guzzlehttp/guzzle package as a dependency:

http://cgit.drupalcode.org/client_error_trace/tree/composer.json?h=7.x-1.x#n13

The guzzlehttp/guzzle dependency should be updated to 6.2.1 to address this issue.

Add a plugin to validate node status in the database compared to memcache

We've seen syncing issues where memcache has a node marked as unpublished, but the database is marked as published. We should add a plugin to explicitly compare the status between loading via the entity cache and via the database.

Add a plugin to support basic HTTP requests

We should add a plugin to support an HTTP request against the provided URL, as well as custom derivatives such as Varnish servers, CDNs, and so on. Let's use Guzzle since it would let us fork off multiple requests and gather them at the end.

I'm not sure the best way to handle this, in that there might be a way with plugin instances to do this cleanly, or we might just want to use a simple settings form.

Add a plugin to check the cache_page bin

If a page is cached by Drupal's page cache, it will be stored in cache_page in MySQL or memcache. We should check the result there to see if we've cached a 4XX.

Add a suggestion to node_access plugin to check if grants need rebuilding