Title: Wrong response codes Last modified: December 25, 2024 --- # Wrong response codes * [Rolf Allard van Hagen](https://wordpress.org/support/users/ravanh/) * (@ravanh) * [1 year, 5 months ago](https://wordpress.org/support/topic/wrong-response-codes/) * Hi, testing this plugin on our site, it runs up many URLs reported with 404, 403 or 400 status but have in reality a 200 or 30x response status. * I tried turning the debug log option ON but that does not seem possible. The switch goes green with the message “Plugin log is now enabled” flashing, then the page reloads with the switch to OFF again… Viewing 1 replies (of 1 total) * Thread Starter [Rolf Allard van Hagen](https://wordpress.org/support/users/ravanh/) * (@ravanh) * [1 year, 4 months ago](https://wordpress.org/support/topic/wrong-response-codes/#post-18215785) * Update: the issue with the debug switch appears to be an incompatibility with Object Caching (in our case: Redis cache with the Litespeed Cache plugin) … but once activated, the debug log does not reveal any useful data for debugging this issue :/ Viewing 1 replies (of 1 total) The topic ‘Wrong response codes’ is closed to new replies. * ![](https://s.w.org/plugins/geopattern-icon/broken-link-finder_004aad.svg) * [Broken Link Checker | Finder](https://wordpress.org/plugins/broken-link-finder/) * [Frequently Asked Questions](https://wordpress.org/plugins/broken-link-finder/#faq) * [Support Threads](https://wordpress.org/support/plugin/broken-link-finder/) * [Active Topics](https://wordpress.org/support/plugin/broken-link-finder/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/broken-link-finder/unresolved/) * [Reviews](https://wordpress.org/support/plugin/broken-link-finder/reviews/) * 1 reply * 1 participant * Last reply from: [Rolf Allard van Hagen](https://wordpress.org/support/users/ravanh/) * Last activity: [1 year, 4 months ago](https://wordpress.org/support/topic/wrong-response-codes/#post-18215785) * Status: not resolved