From 8ae61ce83fab407e9e70e8de71d4e759c0b60ce3 Mon Sep 17 00:00:00 2001 From: "http://smcv.pseudorandom.co.uk/" Date: Thu, 26 May 2011 06:58:04 +0000 Subject: [PATCH] Added a comment --- ...nt_1_02a82e468676ae64374cc91ec87e39d6._comment | 15 +++++++++++++++ 1 file changed, 15 insertions(+) create mode 100644 doc/forum/nginx:_404_plugin_not_working/comment_1_02a82e468676ae64374cc91ec87e39d6._comment diff --git a/doc/forum/nginx:_404_plugin_not_working/comment_1_02a82e468676ae64374cc91ec87e39d6._comment b/doc/forum/nginx:_404_plugin_not_working/comment_1_02a82e468676ae64374cc91ec87e39d6._comment new file mode 100644 index 000000000..982011286 --- /dev/null +++ b/doc/forum/nginx:_404_plugin_not_working/comment_1_02a82e468676ae64374cc91ec87e39d6._comment @@ -0,0 +1,15 @@ +[[!comment format=mdwn + username="http://smcv.pseudorandom.co.uk/" + nickname="smcv" + subject="comment 1" + date="2011-05-26T06:58:04Z" + content=""" +The 404 plugin relies on environment variables set by Apache for 404 handlers. Not all web servers set the same variables (404 handlers aren't a standard feature) so it might need adapting to support nginx. (lighttpd has a similer problem - it doesn't indicate that the request was a 404 in an obvious way.) + +If you temporarily set this (shell!) CGI script as your 404 handler, its output should indicate what variables nginx sets: + + #!/bin/sh + printf \"Content-type: text/plain\r\n\r\n\" + env + +"""]] -- 2.39.5