[Question] Go-server response: Content-Type text/html

Hello,

I have a huge problem with the specification of the response type in openapi. We want to deploy a html web page if the user access the root path /.

The other paths can be encoded as json, but for this case we need the content-type: text/html or application/xml encoding.
However, in any case how I define the response in the .yaml, I get always a json response.

My reponse is described as that:

responses:
        200:
          description: success and returns some html text
          content:
            text/html:
              schema:
                type: string

Anyways, the content-type of this response is always application/json. No matter, if I use the openapi 3.0 specification or swagger 2.0.

I also tried to use the additional argument withXml=True and addResponseHeaders=True

I saw, that the get functions always execute the EncodeJSONResponse function, which is the following:

func EncodeJSONResponse(i interface{}, status *int, headers map[string][]string, w http.ResponseWriter) error {
	wHeader := w.Header()
	if headers != nil {
		for key, values := range headers {
			for _, value := range values {
				wHeader.Add(key, value)
			}
		}
	}
	wHeader.Set("Content-Type", "application/json; charset=UTF-8")
	if status != nil {
		w.WriteHeader(*status)
	} else {
		w.WriteHeader(http.StatusOK)
	}

	return json.NewEncoder(w).Encode(i)
}

It can be seen, that even if you set Content-Type: text/html in the additional response header, it will be overwritten by wHeader.Set("Content-Type", "application/json; charset=UTF-8").

It is really important for us, to return a html page for the user which is using the api.
Otherwise I have to discard my whole project with openapi...

So my question is, if there is one way to return a html response with the go-server.

Hopefully, someone of you can help me.

Best Regards

Start at the generated Go server's get functions and the EncodeJSONResponse entry point shown in the issue. Trace how the OpenAPI response content type reaches the response writer, then verify that a text/html response is preserved without being overwritten by application/json; exercise the behavior with a generated server example.