ESP8266 GET request goes away, but doesn't get a response-error 408

On the esp, a sketch is filled in - a banal sending of the temperature from the sensor to the server. There is no sensor yet, I'm setting up sending. The connection to the server is established, judging by the nginx logs, the request reaches the server, but the response is not formed-error 408. If I go to the link from the browser with the value of the temp variable, the script is processed, the value is written in the database.

#include <ESP8266WiFi.h>
#include <WiFiClientSecure.h>
const char* ssid = "ASUS";//type your ssid
const char* password = "xxx";//type your password
const char* host = "www.мойсервер.org";
void setup() {
Serial.begin(115200);
delay(10);
// Connect to WiFi network
Serial.println();
Serial.println();
Serial.print("Connecting to ");
Serial.println(ssid);

WiFi.begin(ssid, password);

while (WiFi.status() != WL_CONNECTED) {
delay(500);
Serial.print(".");
}
Serial.println("");
Serial.println("WiFi connected");
}
void loop()
{
  WiFiClient client;

  Serial.printf("\n[Connecting to %s ... ", host);
            //  "Подключение к "

  if (client.connect(host, 80))
  {
    Serial.println("connected]");
               //  " подключено"

    Serial.println("[Sending a request]");
               //  "Отправка запроса"
    client.print(String("GET /weather?temp=40") + " HTTP/1.1\r\n" +
                 "Host: мойсервер.org\r\n"+
                 "Connection: close\r\n"
                 );

    Serial.println("[Response:]");
               //  "Ответ:"
    while (client.connected())
    {
      if (client.available())
      {
        String line = client.readStringUntil('\n');
        Serial.println(line);
      }
    }
    client.stop();
    Serial.println("\n[Disconnected]");
               //  "Отключено"
  }
  else
  {
    Serial.println("connection failed!]");
               //  "подключиться не удалось!"
    client.stop();
  }
  delay(5000);
}

Log:

The last line - I go to the page from the browser, the script is on the server it is being worked out. If it makes any difference - on the server application asp.net core, nginx.

Unfortunately, it is not strong in nginx logs.