Reusing broken HTTP connections #49

New issue

Closed

opened 2026-02-17 00:27:56 +00:00 by aniram · 0 comments

aniram commented

2026-02-17 00:27:56 +00:00

Owner

I suspect the various instances of the snippet below in ProjectHandler.RenderProjectsByKeyword is trying to execute the error template after the connection to the client has already been corrupted when trying to execute the previous template. Instead I should just log the error.

     if err := h.templ.ExecuteTemplate(w, "index", d); err != nil {
		fmt.Printf("project.go: could not execute template due to %v", err)
		if err := h.templ.ExecuteTemplate(w, "error", nil); err != nil {
			fmt.Printf("project.go: critical error could not execute error template due to %v", err)
			http.Error(w, "Something went wrong, try again", http.StatusInternalServerError)
		}
	}

project.go: could not execute template due to write tcp [::1]:8000->[::1]:59113: write: broken pipeproject.go: critical error could not execute error template due to write tcp [::1]:8000->[::1]:59113: write: broken pipe2026/02/17 01:16:14 http: superfluous response.WriteHeader call from github.com/marinacompsci/cidadon/internal/handler.(*ProjectHandler).RenderProjectsByKeyword (project.go:208) I suspect the various instances of the snippet below in ProjectHandler.RenderProjectsByKeyword is trying to execute the error template after the connection to the client has already been corrupted when trying to execute the previous template. Instead I should just log the error. ```go if err := h.templ.ExecuteTemplate(w, "index", d); err != nil { fmt.Printf("project.go: could not execute template due to %v", err) if err := h.templ.ExecuteTemplate(w, "error", nil); err != nil { fmt.Printf("project.go: critical error could not execute error template due to %v", err) http.Error(w, "Something went wrong, try again", http.StatusInternalServerError) } } ```