Title: 403 error extensibility
Last modified: April 18, 2024

---

# 403 error extensibility

 *  Resolved [anvilhouse](https://wordpress.org/support/users/anvilhouse/)
 * (@anvilhouse)
 * [2 years, 4 months ago](https://wordpress.org/support/topic/403-error-extensibility-2/)
 * Since AIOWPS offers 404 brute force logging, our team is surprised there is no
   403 log. We have recently started receiving a large amount of 403 reports through
   our cpanel logs, I am however wondering if it would be possible to add this functionality
   either to a new log within the Brute Force section or append these errors into
   the existing 404 log and providing the event code.
   Insight into this would be
   extremely helpful as it would offer a far easier method to diagnose this issue
   on our WP sites.

Viewing 2 replies - 1 through 2 (of 2 total)

 *  Plugin Support [hjogiupdraftplus](https://wordpress.org/support/users/hjogiupdraftplus/)
 * (@hjogiupdraftplus)
 * [2 years, 4 months ago](https://wordpress.org/support/topic/403-error-extensibility-2/#post-17698200)
 * Hi [@anvilhouse](https://wordpress.org/support/users/anvilhouse/)
 * The 403 Forbidden Error means you’re trying to open in your web browser a resource
   that you’re not allowed to access.
 * So for All 403 type error log at AIOS pluign level possible or not have check
   in details.
 * I will create internal ticket for this and get back to you.
 * Regards
 *  Plugin Support [hjogiupdraftplus](https://wordpress.org/support/users/hjogiupdraftplus/)
 * (@hjogiupdraftplus)
 * [2 years, 3 months ago](https://wordpress.org/support/topic/403-error-extensibility-2/#post-17750905)
 * Hi [@anvilhouse](https://wordpress.org/support/users/anvilhouse/),
 * If Apache / .htaccess is raising 403 errors it will not be possible to capture
   those 403 errors in a WordPress plugin. It might be considered feature seems 
   not working properly.
 * So we are right now not considering working on this suggestion.
 * The AIOS firewall rules raising 403 errors will have a separate log. we may work
   in future for that.
 * Regards

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘403 error extensibility’ is closed to new replies.

 * ![](https://ps.w.org/all-in-one-wp-security-and-firewall/assets/icon-256x256.
   png?rev=2798307)
 * [All-In-One Security (AIOS) – Security and Firewall](https://wordpress.org/plugins/all-in-one-wp-security-and-firewall/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/all-in-one-wp-security-and-firewall/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/all-in-one-wp-security-and-firewall/)
 * [Active Topics](https://wordpress.org/support/plugin/all-in-one-wp-security-and-firewall/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/all-in-one-wp-security-and-firewall/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/all-in-one-wp-security-and-firewall/reviews/)

## Tags

 * [extend](https://wordpress.org/support/topic-tag/extend/)

 * 2 replies
 * 2 participants
 * Last reply from: [hjogiupdraftplus](https://wordpress.org/support/users/hjogiupdraftplus/)
 * Last activity: [2 years, 3 months ago](https://wordpress.org/support/topic/403-error-extensibility-2/#post-17750905)
 * Status: resolved