Lighttpd 404 Error Handler
Contents |
5 years ago 404 not found lighttpd Hi All,I need customize 501 error
Lighttpd Index.html 404
pages, if i wrote in "lighttpd.conf" : server.error-handler-404 =
Lighttpd Setup
"/error.php" -- WORKserver.error-handler-401 = "/error.php" -- NOT WORKserver.error-handler-501 = "/error.php" -- NOT WORK... How
Lighttpd Redirect
can I do customize page with other errors, not only 404 error? Replies (2) RE: Customize error pages, not only 404 error. - Added by spaam about 5 lighttpd url rewrite years ago the error handler only works for 404..http://redmine.lighttpd.net/wiki/lighttpd/Server.errorfile-prefixDetails something for you to read. RE: Customize error pages, not only 404 error. - Added by sinoptik about 5 years ago I know about this, but this way use only static page. I need to show my error code (for example 200 for any error). Who can tell me how to do, to act Lighttpd my script for any errors and return my error codes. Thanks. (1-2/2) Loading... Powered by Redmine © 2006-2016 Jean-Philippe Lang
without target version Feature #1220 Support lighttpd redirect all requests external 404 error page (server.error-handler-404) Added lighttpd log by joungkyun over 9 years ago. Updated about 8 lighttpd directory listing years ago. Status:WontfixPriority:NormalAssignee:-Category:coreTarget version:1.4.20Start date:Due date:% Done:0% Missing in 1.5.x: Description lighttpd does not redirect http://redmine.lighttpd.net/boards/2/topics/4639 foreign 404 error page. This patch is enable to redirect 404 error page to foreign web page.for example: server.error-handler-404 = "http://domain.com/errs/404.html" lighttpd-1.4.15-foreign-404-page.patch View - redirect 404 error page to https://redmine.lighttpd.net/issues/1220 foreign web page (5.56 KB) joungkyun, 2007-06-07 08:40 lighttpd-foreign-404.patch View - fixed wrong http status on HTTP/1.0 (3.62 KB) joungkyun, 2007-06-14 05:24 History #1 Updated by stbuehler about 8 years ago Status changed from New to Fixed Resolution set to wontfix I don't like the patch; and it isn't necessary anyway. url.redirect = ( "^/notexisting" => "http://domain.com/errs/404.html", ) server.error-handler-404 = "/notexisting" #2 Updated by stbuehler about 8 years ago Status changed from Fixed to Wontfix Also available in: Atom Loading... Powered by Redmine © 2006-2016 Jean-Philippe Lang
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies http://stackoverflow.com/questions/7513650/lighttpd-404-page-does-not-return-404-status of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 6.2 million programmers, just like you, helping each other. Join them; it only takes a minute: lighttpd redirect Sign up lighttpd: 404 page does not return 404 status up vote 2 down vote favorite I'm using a lighttpd 404 error handler, with a static 404 page. The entire conf file looks like this: server.document-root = "/home/www/local/www/mysite/html" url.rewrite = ( "^(.*)/($|\?.*)" => "$1/index.html", "^(.*)/([^.?]+)($|\?.*)$" => "$1/$2.html" ) server.error-handler-404 = "/404.html" $HTTP["scheme"] == "http" { url.redirect = ( "^/blog.html$" => "/blog/", // various lighttpd 404 error individual redirects ) } $HTTP["scheme"] == "https" { $HTTP["url"] !~ "^/blog/admin/" { url.redirect = ( "^/(.*)" => "http://www.mysite.com/$1" ) } } However, when I go to an address that should 404, I do correctly see our 404 page, but the status code is 200. The lighttpd docs say that you should get a 404 status code if using a static page. I think we're using a static page, but could something about the way we're redirecting mean that we're actually not? Sorry for the newbie question. webserver http-status-code-404 lighttpd http-status-codes share|improve this question asked Sep 22 '11 at 10:57 Richard 6,8561678127 add a comment| 1 Answer 1 active oldest votes up vote 3 down vote accepted Fixed this by using server.errorfile-prefix instead - think it is simply a bug in server.error-handler-404. Seems to be a known bug in some versions of lighttpd. I was actually using a later version than 1.4.17, but still seeing the same problem. share|improve this answer answered Sep 28 '11 at 8:23 Richard 6,8561678127 1 Thanks, this sorted my problem. I am also on the later version but have t