> > "file not found" should return http code 404. elogd returns code 200 together
> > with a page containing text "404 not found". This pollutes the browser cache
> > with wrong content (in this case, we are trying to load a css file, and the browser
> > is trying to use text "404 not found" as if it were a css. bad. file not found
> > should return http code 404. K.O.
>
> Yes. That's quite a problem when interacting with ELOG programmatically. Only way to
> find whether response succeeded or failed with 404 is to parse response body
>
> When file is not found send_file_direct calls show_html_header which in turn calls
> show_http_header which sets HTTP code 200 unconditionally. It's reasonably easy to
> patch around.
I fixed the code to properly return "404 Not Found" in case a non-existing file is requested.
Stefan |