Bug 58985 - Support sending 451 status from RewriteRule
Summary: Support sending 451 status from RewriteRule
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: Core (show other bugs)
Version: 2.5-HEAD
Hardware: PC All
: P2 enhancement (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
Keywords: PatchAvailable
Depends on:
Reported: 2016-02-09 19:12 UTC by Yehuda Katz
Modified: 2016-02-16 17:43 UTC (History)
1 user (show)

trunk patch (2.09 KB, patch)
2016-02-09 19:13 UTC, Yehuda Katz
Details | Diff
2.4 patch (2.09 KB, patch)
2016-02-09 19:29 UTC, Yehuda Katz
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Yehuda Katz 2016-02-09 19:12:26 UTC
mod_rewrite (and possibly other modules) can't send a 451 error unless it is supported by the server. This is a basically standard patch to bring the status codes up to http://www.iana.org/assignments/http-status-codes/http-status-codes.xml (similar to #53929)

Patch attached.

Only question is about error page text - the RFC says it SHOULD be detailed about why the content is blocked and we can't really do that so easily in the default message.
Comment 1 Yehuda Katz 2016-02-09 19:13:04 UTC
Created attachment 33538 [details]
trunk patch
Comment 2 Yehuda Katz 2016-02-09 19:29:03 UTC
Created attachment 33539 [details]
2.4 patch
Comment 3 Jim Jagielski 2016-02-16 17:43:01 UTC
Added to trunk