Project

General

Profile

Actions
Copy link

Bug #168

closed

server.error-handler-404 Problem.

Added by Anonymous almost 20 years ago. Updated over 18 years ago.

Status:
Fixed
Priority:
Urgent
Category:
core
Target version:
-
ASK QUESTIONS IN Forums:

Description

In meiner config hatte ich:

Server.error-handler-404 = "/dienste/singles/src/keinbild_thumb120x180.jpeg"

eingetragen.

Trozdem kommt weiterhin die "normale" 404 Seite. Im Errorlog sind keine
Spuren zu finden. Ein Strace gibt follgendes aus:


read(213, "GET /3fs.jpeg HTTP/1.1\r\nHost: st"..., 4159) = 463                                                            
stat64("/var/www/3fs.jpeg", 0x8108368)  = -1 ENOENT (No such file or directory)                                           
stat64("/var/www/3fs.jpeg", 0xbfa70560) = -1 ENOENT (No such file or directory)                                           
stat64("/var/www/dienste/singles/src/keinbild_thumb120x180.jpeg", {st_mode=S_IFREG|0644, st_size=3841, ...}) = 0          
open("/var/www/dienste/singles/src/keinbild_thumb120x180.jpeg", O_RDONLY|O_LARGEFILE) = 235                               
setsockopt(213, SOL_TCP, TCP_CORK, [1], 4) = 0                                                                            
writev(213, [{"HTTP/1.1 404 Not Found\r\nDate: Mo"..., 156}, {"<?xml version=\"1.0\" encoding=\"is"..., 345}], 2) = 501

-- ruben

Actions
Copy link
 #1

Updated by jan almost 20 years ago

  • Status changed from New to Fixed
  • Resolution set to fixed

fixed in r489

Actions
Copy link
 #2

Updated by Anonymous almost 20 years ago

  • Status changed from Fixed to Need Feedback
  • Resolution deleted (fixed)

Hi Jan,
Thanks for trying to fix it in 1.3.16 but this creates another problem with using 200 status code. This means all files that are missing also get logged in access.log as status 200 so now have no way of knowing from the access.log which all files are missing/broken on the filesystem. This is a really severe bug for most companies.

The best solution is a 302 type redirect that apache had. If not at least the error log MUST document a 404 in error.log when a 404 handler static file is served.

-- nycfresh

Actions
Copy link

Also available in: Atom