Handle unexpected statuscodes from the log provider

**What**
- Use NotImplemented when we get a 404 from the log provider.  When we
get a 200, process the log request, as normal.  For all other status
codes, return a sever error with a message stating that the
response was unexpected.  The message will contain the original status
code to assist with debugging

Signed-off-by: Lucas Roesler <roesler.lucas@gmail.com>

gateway/handlers/logs.go

@@ -2,6 +2,7 @@ package handlers
 
 import (
 	"context"
+	"fmt"
 	"io"
 	"log"
 	"net/http"
@@ -66,6 +67,11 @@ func NewLogHandlerFunc(logProvider url.URL, timeout time.Duration) http.HandlerF
 		}
 		defer logResp.Body.Close()
 
+		switch logResp.StatusCode {
+		case http.StatusNotFound, http.StatusNotImplemented:
+			w.WriteHeader(http.StatusNotImplemented)
+			return
+		case http.StatusOK:
 			// watch for connection closures and stream data
 			// connections and contexts should have cancel methods deferred already
 			select {
@@ -78,6 +84,9 @@ func NewLogHandlerFunc(logProvider url.URL, timeout time.Duration) http.HandlerF
 				log.Printf("LogProxy: client connection closed")
 				return
 			}
+		default:
+			http.Error(w, fmt.Sprintf("unknown log request error (%v)", logResp.StatusCode), http.StatusInternalServerError)
+		}
 
 		return
 	}