WordPress.org
Get WordPress

Make WordPress Core

Changes between Initial Version and Version 3 of Ticket #47945


Ignore:
Timestamp:
08/29/2019 02:21:13 AM (5 years ago)
Author:
SergeyBiryukov
Comment:

Hi @flymike, welcome to WordPress Trac! Thanks for the ticket.

As #35835 is essentially the same issue and already has some comments, it's better to keep the discussion in one place.

If there's consensus that it should be reconsidered, the ticket can be reopened and marked as an enhancement. Let's continue there?

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #47945

    • Property Status changed from new to closed
    • Property Resolution changed from to duplicate
    • Property Milestone changed from Awaiting Review to

  • Ticket #47945 – Description

    initial v3  
    11Some hacker has discovered many of the WordPress files containing calls to _deprecated_file() and is inundating my server with direct GET requests to them.
    2 Because that function is not defined in Wordpress, Apache returns status 500 and - because, as an administrator, I want to be informed of status 500 - my inbox is deluged with alerts.
     2Because that function is not defined in WordPress, Apache returns status 500 and - because, as an administrator, I want to be informed of status 500 - my inbox is deluged with alerts.
    33I would block the originating IPs but they'e all different, so coming from spambots. And the advantage to the hacker eludes me completely - but it is what it is, and I have to deal with it.
    44Couldn't Wordpress handle calls to deprecated files/functions a little more elegantly? Like it does with direct calls to other files which should not be accessed directly - with status 200 and zero bytes?