Website Response langsam von Billi, der Brillenbär, 10.02.2020 21:40

Website Response langsam

Billi, der Brillenbär 10.02.2020 21:40

Schönen guten Tag. Ich prüfe mit curl für einen Freund eine Webseite, die per NGINX ausgeliefert wird. Die Response-Zeit dieser Seite ist sehr langsam. Ich poste hier mal die Response, weil ich streckenweise ein Problem habe, diese zu verstehen.

% Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0*   Trying <IP GELÖSCHT>...
* TCP_NODELAY set
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0* Connected to www.example.com (<IP GELÖSCHT>) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
} [5 bytes data]
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
} [512 bytes data]
* TLSv1.3 (IN), TLS handshake, Server hello (2):
{ [122 bytes data]
* TLSv1.3 (IN), TLS Unknown, Certificate Status (22):
{ [1 bytes data]
* TLSv1.3 (IN), TLS handshake, Unknown (8):
{ [19 bytes data]
* TLSv1.3 (IN), TLS Unknown, Certificate Status (22):
{ [1 bytes data]
* TLSv1.3 (IN), TLS handshake, Certificate (11):
{ [4507 bytes data]
* TLSv1.3 (IN), TLS Unknown, Certificate Status (22):
{ [1 bytes data]
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
{ [264 bytes data]
* TLSv1.3 (IN), TLS Unknown, Certificate Status (22):
{ [1 bytes data]
* TLSv1.3 (IN), TLS handshake, Finished (20):
{ [52 bytes data]
* TLSv1.3 (OUT), TLS change cipher, Client hello (1):
} [1 bytes data]
* TLSv1.3 (OUT), TLS Unknown, Certificate Status (22):
} [1 bytes data]
* TLSv1.3 (OUT), TLS handshake, Finished (20):
} [52 bytes data]
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: OU=Domain Control Validated; OU=PositiveSSL; CN=example.com
*  start date: Jun 25 00:00:00 2019 GMT
*  expire date: Jun 24 23:59:59 2020 GMT
*  subjectAltName: host "www.example.com" matched cert's "www.example.com"
*  issuer: gelöscht
*  SSL certificate verify ok.
* Using HTTP2, server supports multi-use
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
} [5 bytes data]
* TLSv1.3 (OUT), TLS Unknown, Unknown (23):
} [1 bytes data]
* TLSv1.3 (OUT), TLS Unknown, Unknown (23):
} [1 bytes data]
* TLSv1.3 (OUT), TLS Unknown, Unknown (23):
} [1 bytes data]
* Using Stream ID: 1 (easy handle 0x562f800fa4b0)
} [5 bytes data]
* TLSv1.3 (OUT), TLS Unknown, Unknown (23):
} [1 bytes data]

> GET /alte-schuhe/ HTTP/2
> Host: www.example.comf
> User-Agent: curl/7.58.0
> Accept: */*
> 

{ [5 bytes data]
* TLSv1.3 (IN), TLS Unknown, Certificate Status (22):
{ [1 bytes data]
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
{ [265 bytes data]
* TLSv1.3 (IN), TLS Unknown, Certificate Status (22):
{ [1 bytes data]
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
{ [265 bytes data]
* TLSv1.3 (IN), TLS Unknown, Unknown (23):
{ [1 bytes data]
* Connection state changed (MAX_CONCURRENT_STREAMS updated)!
} [5 bytes data]
* TLSv1.3 (OUT), TLS Unknown, Unknown (23):
} [1 bytes data]
  0     0    0     0    0     0      0      0 --:--:--  0:00:02 --:--:--     0* TLSv1.3 (IN), TLS Unknown, Unknown (23):
{ [1 bytes data]
< HTTP/2 200 
< server: nginx
< date: Mon, 10 Feb 2020 20:33:54 GMT
< content-type: text/html; charset=UTF-8
< content-length: 295034
< vary: Accept-Encoding
< x-powered-by: PHP/7.2.27
< expires: Thu, 19 Nov 1981 08:52:00 GMT
< cache-control: no-store, no-cache, must-revalidate, no-cache, private
< pragma: no-cache
< x-content-digest: en560asdfeasdfasd2a8f1daf6284a80ff58137aa7cc5a0412931d7
< age: 1925
< set-cookie: session-1=5c912e2a85a1asdfeasdfasdff8de4a50b877cbf3c6aae6621; path=/; secure; HttpOnly
< set-cookie: x-cache-context-hash=deleted; expires=Mon, 10-Feb-2020 20:33:52 GMT; Max-Age=0; path=/
< set-cookie: nocache=deleted; expires=Mon, 10-Feb-2020 20:33:52 GMT; Max-Age=0; path=/
< vary: Accept-Encoding,User-Agent
< x-frame-options: SAMEORIGIN
< x-cache-status: MISS

< 
{ [7028 bytes data]
* TLSv1.3 (IN), TLS Unknown, Unknown (23):
{ [1 bytes data]
* TLSv1.3 (IN), TLS Unknown, Unknown (23):
{ [1 bytes data]
* TLSv1.3 (IN), TLS Unknown, Unknown (23):
{ [1 bytes data]
* TLSv1.3 (IN), TLS Unknown, Unknown (23):
{ [1 bytes data]
* TLSv1.3 (IN), TLS Unknown, Unknown (23):
{ [1 bytes data]
* TLSv1.3 (IN), TLS Unknown, Unknown (23):
{ [1 bytes data]
* TLSv1.3 (IN), TLS Unknown, Unknown (23):
{ [1 bytes data]
* TLSv1.3 (IN), TLS Unknown, Unknown (23):
{ [1 bytes data]
* TLSv1.3 (IN), TLS Unknown, Unknown (23):
{ [1 bytes data]
 27  288k   27 80756    0     0  23360      0  0:00:12  0:00:03  0:00:09 23353* TLSv1.3 (IN), TLS Unknown, Unknown (23):
{ [1 bytes data]
* TLSv1.3 (IN), TLS Unknown, Unknown (23):
{ [1 bytes data]
* TLSv1.3 (IN), TLS Unknown, Unknown (23):
{ [1 bytes data]
* TLSv1.3 (IN), TLS Unknown, Unknown (23):
{ [1 bytes data]
* TLSv1.3 (IN), TLS Unknown, Unknown (23):
{ [1 bytes data]
* TLSv1.3 (IN), TLS Unknown, Unknown (23):
{ [1 bytes data]
* TLSv1.3 (IN), TLS Unknown, Unknown (23):
{ [1 bytes data]
* TLSv1.3 (IN), TLS Unknown, Unknown (23):
{ [1 bytes data]
* TLSv1.3 (IN), TLS Unknown, Unknown (23):
{ [1 bytes data]
* TLSv1.3 (IN), TLS Unknown, Unknown (23):
{ [1 bytes data]
* TLSv1.3 (IN), TLS Unknown, Unknown (23):
{ [1 bytes data]
* TLSv1.3 (IN), TLS Unknown, Unknown (23):
{ [1 bytes data]
* TLSv1.3 (IN), TLS Unknown, Unknown (23):
{ [1 bytes data]
* TLSv1.3 (IN), TLS Unknown, Unknown (23):
{ [1 bytes data]
* TLSv1.3 (IN), TLS Unknown, Unknown (23):
{ [1 bytes data]
* TLSv1.3 (IN), TLS Unknown, Unknown (23):
{ [1 bytes data]
* TLSv1.3 (IN), TLS Unknown, Unknown (23):
{ [1 bytes data]
100  288k  100  288k    0     0  81478      0  0:00:03  0:00:03 --:--:-- 81456
* Connection #0 to host www.example.com left intact

Insbesondere das häufige * TLSv1.3 (IN), TLS Unknown, Unknown (23) verstehe ich nicht. Es scheint ja ein Problem mit TLS zu geben, so wie ich das sehe.

IP und Domain habe ich mal rausgelöscht. Vielleicht hat jemand ja eine Idee, ich bin ratlos.

Bei der Stelle "MAX_CONCURRENT_STREAMS updated", dauert es ca. 1 Sekunde, bis es weitergeht.

viele Grüße der Brillenbär

Beitrag melden

– Informationen zu den Bewertungsregeln

Website Response langsam
Raketendiagnostiker 19.02.2020 13:50

nginx

webserver
– Informationen zu den Bewertungsregeln
Meldungen à la „TLSv1.3 (IN), TLS Unknown, Unknown (23)“ kann auch der Client verursachen.
- Ohne URL kann ich nichts untersuchen. Andere auch nicht…
Beitrag melden

–
Informationen zu den Bewertungsregeln

SELFHTML Forum - Ergänzung zur Dokumentation Übersicht

Billi, der Brillenbär: Website Response langsam