K8s API服務器400錯誤

Question

我在K8s 1.5.1 API服務器上看到一些奇怪的行爲。甲GET請求是用於/api送出，200響應到達有序，但隨後的ACK之後是400和FIN：

23:12:13.032057 IP localhost.52218 > localhost.http-alt: Flags [P.], seq 1:169, ack 1, win 86, options [nop,nop,TS val 3882137617 ecr 3882136607], length 168: HTTP: GET /api HTTP/1.1 
23:12:13.032078 IP localhost.http-alt > localhost.52218: Flags [.], ack 169, win 88, options [nop,nop,TS val 3882137617 ecr 3882137617], length 0 
23:12:13.032569 IP localhost.http-alt > localhost.52218: Flags [P.], seq 1:243, ack 169, win 88, options [nop,nop,TS val 3882137618 ecr 3882137617], length 242: HTTP: HTTP/1.1 200 OK 
23:12:13.032584 IP localhost.52218 > localhost.http-alt: Flags [.], ack 243, win 88, options [nop,nop,TS val 3882137618 ecr 3882137618], length 0 
23:12:13.032621 IP localhost.http-alt > localhost.52218: Flags [P.], seq 243:331, ack 169, win 88, options [nop,nop,TS val 3882137618 ecr 3882137618], length 88: HTTP: HTTP/1.1 400 Bad Request 
23:12:13.032633 IP localhost.52218 > localhost.http-alt: Flags [.], ack 331, win 88, options [nop,nop,TS val 3882137618 ecr 3882137618], length 0 
23:12:13.032666 IP localhost.http-alt > localhost.52218: Flags [F.], seq 331, ack 169, win 88, options [nop,nop,TS val 3882137618 ecr 3882137618], length 0 

相同的客戶端代碼運行良好早期版本的API服務器的。任何人都可以闡明這種行爲？

Answer 1

好吧，我發現的罪魁禍首 - 請求具有HTTP基本身份驗證標題結尾\n。雖然請求作爲一個整體用CRLFCRLF正確結束，並且之後沒有結尾垃圾，但API服務器以某種方式將\n解釋爲新請求的開始。 Kubernetes API服務器錯誤？