Opened 2 years ago

Last modified 21 months ago

#17619 new enhancement

Soft 404 at /wp-content/plugins/

Reported by: miqrogroove Owned by:
Priority: normal Milestone: Awaiting Review
Component: General Version:
Severity: minor Keywords: has-patch
Cc: info@…, admin@…

Description

/wp-content/plugins/index.php would be better written with a proper 404.

<?php
header('HTTP/1.0 404 Not Found'); // Silence is golden.
?>

Attachments (3)

17619.diff (341 bytes) - added by BenChapman 2 years ago.
Adds a 404 error message
17619.patch (664 bytes) - added by jakub.tyrcha 23 months ago.
17619.2.patch (1005 bytes) - added by jakub.tyrcha 23 months ago.

Download all attachments as: .zip

Change History (12)

Shouldn't it technically be a 403?

Technically, there is nothing in the response entity, so either 403 or 404 is appropriate.

  • Cc info@… added

Why not 410? Nobody should come back, no?

As per RFC2616 if a reason is to be given for denying access then 403 should be used, otherwise 404 should be used. In this case I would say 403 would be the better response code with a reason included for forbidding access.

Last edited 2 years ago by BenChapman (previous) (diff)

Adds a 404 error message

  • Cc admin@… added

If this is going to change, then it should change for all wp-content directories, i.e., /themes and /uploads also.

  • Type changed from defect (bug) to enhancement

Why should we include this in the uploads/ directory as well?

  • Keywords has-patch added

I feel that a 403 would be a more appropriate response since there is actually a directory, just not that one permit access to access it.

Last edited 21 months ago by edwardw (previous) (diff)
Note: See TracTickets for help on using tickets.