It's hard to get excited about this.

Something like this?

var ErrorHandler func(w http.ResponseWriter, error string, code int) = func(w ResponseWriter, error string, code int) {
    w.Header().Set("Content-Type", "text/plain; charset=utf-8")
    w.WriteHeader(code)
    fmt.Fprintln(w, error)
}

func Error(w ResponseWriter, error string, code int) {
    ErrorHandleR(w, error, code)
}

Seems a bit gross TBH. I don't know that we want to add yet another hook.

It so easy to write your own functions.

@rsc how would one write an error handler for the not found case and use that in the built-in file server instead of the NotFound response? Something so I wouldn't need https://github.com/Masterminds/go-fileserver

Give ServeContent or whatever a ResponseWriter which intercepts the 404/403/500/etc and writes its own message.

@bradfitz that's an interesting take I had not thought of. It should work.

My issue with it is that it's not a good separation of concerns. It's a hack to work around this limitation. Something that's responsible with content now needs to look for certain types of responses and override the output to something custom.

It would be nice to have a clean solution.

There's also this and this that seem to bypass the ResponseWriter altogether.