{"id":55407,"date":"2020-01-20T00:00:00","date_gmt":"2020-01-19T21:00:00","guid":{"rendered":"https:\/\/prohoster.info\/blog\/blog_prohoster\/nginx-kak-pobedit-response_status-0"},"modified":"2020-02-18T14:03:31","modified_gmt":"2020-02-18T11:03:31","slug":"nginx-kak-pobedit-response_status-0","status":"publish","type":"post","link":"https:\/\/prohoster.info\/de\/blog\/administrirovanie\/nginx-kak-pobedit-response_status-0","title":{"rendered":"[Nginx] \u041a\u0430\u043a \u043f\u043e\u0431\u0435\u0434\u0438\u0442\u044c response_status = 0","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Ein Artikel aus der Kategorie 'Notizen am Rande'.<\/p>\n

TL:DR:<\/b><\/p>\n

http2_max_field_size 8k; # das wird helfen!<\/code><\/pre>\n
In einem unserer Projekte, nach einer \u00c4nderung in der internen Logik des Backends, beobachtete ich einen seltsamen response_code in den Logs, n\u00e4mlich \u2014 0. In den Logs sieht das ungef\u00e4hr so aus:<\/p>\n
{\n  "timestamp": "2020-01-17T08:41:51+00:00",\n  "remote_addr": "zzz.zzz.zzz.zzz",\n  "request_time": 0,\n  "upstream_response_time": "",\n  "upstream_header_time": "",\n  "http_accept_language": "-language",\n  "response_status": 0,\n  "request": "",\n  "host": "example.com",\n  "upstream_addr": "",\n  "http_referrer": "",\n  "request_length": 5854,\n  "bytes_sent": 0,\n  "http_user_agent": ""\n}\n<\/code><\/pre>\n
<\/a><\/noindex>
\nDas Studium der Dokumentation und das Googeln zu diesem Thema hat mir nichts gebracht \u2013 da behauptet wird, dass ein solches Verhalten auftritt, wenn der Client die Verbindung schlie\u00dft, ohne Header zu \u00fcbermitteln. Und die ganze Exotik bez\u00fcglich der Buffergr\u00f6\u00dfe f\u00fcr wsgi_, was in unserem Fall \u00fcberhaupt nicht passte.<\/p>\n
Insgesamt kamen wir zu der Entscheidung, dass das Problem \u2014 kein Problem ist, da es bei unseren Volumina v\u00f6llig unkritisch ist.<\/p>\n
Genau bis zu dem Moment, als ich mit dem n\u00e4chsten Problem konfrontiert wurde: In einigen F\u00e4llen \u00f6ffnen sich die Links problemlos \u00fcber http, funktionieren aber \u00fcberhaupt nicht \u00fcber https und erzeugen die wunderbare Meldung: Connection #0 to host example.com left intact
\ncurl: (52) Leere Antwort vom Server<\/p>\n
In den Protokollen konnte dieses Problem nur \u00fcber die IP nachverfolgt werden \u2014 weder Requests noch andere Daten, wie im obigen Beispiel zu sehen ist, sind vorhanden. Nur der ber\u00fcchtigte Status 0, aber ich wei\u00df, dass ich die Anfrage nicht unterbrochen habe! Ich begann zu untersuchen, was schiefgehen k\u00f6nnte. Und es stellte sich als ganz einfach heraus:<\/p>\n
listen 443 ssl<\/a> http2<\/b> backlog=8192;<\/i><\/p>\n
So, wenn http2 f\u00fcr SSL-Verbindungen verwendet wird, reicht es nicht aus, nur die Anfrage-Puffer zu konfigurieren; sie m\u00fcssen auch im ngx_http_v2_module konfiguriert werden, und zwar:<\/p>\n
Syntax:\thttp2_max_field_size size;\nVoreinstellung:\thttp2_max_field_size 4k;\nKontext:\thttp, server\n<\/code><\/pre>\n
\nBegrenzt die maximale Gr\u00f6\u00dfe des \u00fcber HPACK komprimierten Anfrage-Headers. Die Beschr\u00e4nkung gilt gleicherma\u00dfen f\u00fcr den Namen und den Wert. Bei Verwendung der Huffman-Codierung kann die tats\u00e4chliche Gr\u00f6\u00dfe der entpackten Namen und Werte gr\u00f6\u00dfer sein. Die voreingestellte Begrenzung ist f\u00fcr die meisten Anfragen geeignet.<\/i><\/p>\n
Im Grunde ist es das. Und warum? Weil die URL zu lang war \u2014 l\u00e4nger als die besagten 4k.<\/p>\n
Wenn man sie beispielsweise auf 8kb (oder so viel, wie man sicher braucht) setzt, l\u00f6st man das Problem.
\nSo steht's.
\n
Quelle: habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"
\u0421\u0442\u0430\u0442\u044c\u044f \u0438\u0437 \u0440\u0430\u0437\u0440\u044f\u0434\u0430 \u00ab\u0437\u0430\u043c\u0435\u0442\u043a\u0438 \u043d\u0430 \u043f\u043e\u043b\u044f\u0445\u00bb. TL:DR: http2_max_field_size 8k; # \u0432\u0441\u0435\u0445 \u0441\u043f\u0430\u0441\u0435\u0442! \u041d\u0430 \u043e\u0434\u043d\u043e\u043c \u0438\u0437 \u043f\u0440\u043e\u0435\u043a\u0442\u043e\u0432, \u043f\u043e\u0441\u043b\u0435 \u0438\u0437\u043c\u0435\u043d\u0435\u043d\u0438\u044f \u043d\u0435\u043a\u043e\u0442\u043e\u0440\u043e\u0439 \u0432\u043d\u0443\u0442\u0440\u0435\u043d\u043d\u0435\u0439 \u043b\u043e\u0433\u0438\u043a\u0438 \u0431\u0435\u043a\u0435\u043d\u0434\u0430, \u043d\u0430\u0447\u0430\u043b \u043d\u0430\u0431\u043b\u044e\u0434\u0430\u0442\u044c \u0441\u0442\u0440\u0430\u043d\u043d\u044b\u0439 response_code \u0432 \u043b\u043e\u0433\u0430\u0445, \u0430 \u0438\u043c\u0435\u043d\u043d\u043e \u2014 0. \u0412 \u043b\u043e\u0433\u0430\u0445 \u0432\u044b\u0433\u043b\u044f\u0434\u0438\u0442 \u043f\u0440\u0438\u043c\u0435\u0440\u043d\u043e \u0442\u0430\u043a: { "timestamp": "2020-01-17T08:41:51+00:00", "remote_addr": "zzz.zzz.zzz.zzz", "request_time": 0, "upstream_response_time": "", "upstream_header_time": "", "http_accept_language": "-language", "response_status": 0, "request": "", "host": […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-55407","post","type-post","status-publish","format-standard","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\n","aioseo_head_json":{"title":"\ud83e\udd47[Nginx] \u041a\u0430\u043a \u043f\u043e\u0431\u0435\u0434\u0438\u0442\u044c response_status = 0 | ProHoster","description":"Artikel aus der Kategorie \u201eRandnotizen\u201c. TL:DR: http2_max_field_size 8k; # retten Sie alle! In einem meiner Projekte beobachtete ich nach einer \u00c4nderung in der internen Logik des Backends einen seltsamen response_code in den Logs, und zwar \u2014 0. In den Logs sieht das etwa so aus: { \"timestamp\": \"2020-01-17T08:41:51+00:00\", \"remote_addr\": \"zzz.zzz.zzz.zzz\", \"request_time\": 0, \"upstream_response_time\": \"\", \"upstream_header_time\": \"\", \"http_accept_language\": \"-language\", \"response_status\": 0, \"request\": \"\", \"host\": \"example.com\",","canonical_url":"https:\/\/prohoster.info\/de\/blog\/administrirovanie\/nginx-kak-pobedit-response_status-0","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"de_DE","og:site_name":"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b","og:type":"article","og:title":"\ud83e\udd47[Nginx] \u041a\u0430\u043a \u043f\u043e\u0431\u0435\u0434\u0438\u0442\u044c response_status = 0 | ProHoster","og:description":"\u0421\u0442\u0430\u0442\u044c\u044f \u0438\u0437 \u0440\u0430\u0437\u0440\u044f\u0434\u0430 \u00ab\u0437\u0430\u043c\u0435\u0442\u043a\u0438 \u043d\u0430 \u043f\u043e\u043b\u044f\u0445\u00bb. TL:DR:http2_max_field_size 8k; # \u0432\u0441\u0435\u0445 \u0441\u043f\u0430\u0441\u0435\u0442! \u041d\u0430 \u043e\u0434\u043d\u043e\u043c \u0438\u0437 \u043f\u0440\u043e\u0435\u043a\u0442\u043e\u0432, \u043f\u043e\u0441\u043b\u0435 \u0438\u0437\u043c\u0435\u043d\u0435\u043d\u0438\u044f \u043d\u0435\u043a\u043e\u0442\u043e\u0440\u043e\u0439 \u0432\u043d\u0443\u0442\u0440\u0435\u043d\u043d\u0435\u0439 \u043b\u043e\u0433\u0438\u043a\u0438 \u0431\u0435\u043a\u0435\u043d\u0434\u0430, \u043d\u0430\u0447\u0430\u043b \u043d\u0430\u0431\u043b\u044e\u0434\u0430\u0442\u044c \u0441\u0442\u0440\u0430\u043d\u043d\u044b\u0439 response_code \u0432 \u043b\u043e\u0433\u0430\u0445, \u0430 \u0438\u043c\u0435\u043d\u043d\u043e \u2014 0. \u0412 \u043b\u043e\u0433\u0430\u0445 \u0432\u044b\u0433\u043b\u044f\u0434\u0438\u0442 \u043f\u0440\u0438\u043c\u0435\u0440\u043d\u043e \u0442\u0430\u043a: { "timestamp": "2020-01-17T08:41:51+00:00", "remote_addr": "zzz.zzz.zzz.zzz", "request_time": 0, "upstream_response_time": "", "upstream_header_time": "", "http_accept_language": "-language", "response_status": 0, "request": "", "host": "example.com",","og:url":"https:\/\/prohoster.info\/de\/blog\/administrirovanie\/nginx-kak-pobedit-response_status-0","og:image":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:secure_url":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:width":350,"og:image:height":350,"article:published_time":"2020-01-19T21:00:00+00:00","article:modified_time":"2020-02-18T11:03:31+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"55407","title":null,"description":null,"keywords":null,"keyphrases":null,"primary_term":null,"canonical_url":null,"og_title":null,"og_description":null,"og_object_type":"default","og_image_type":"default","og_image_url":null,"og_image_width":null,"og_image_height":null,"og_image_custom_url":null,"og_image_custom_fields":null,"og_video":null,"og_custom_url":null,"og_article_section":null,"og_article_tags":null,"twitter_use_og":false,"twitter_card":"default","twitter_image_type":"default","twitter_image_url":null,"twitter_image_custom_url":null,"twitter_image_custom_fields":null,"twitter_title":null,"twitter_description":null,"schema":{"blockGraphs":[],"customGraphs":[],"default":{"data":{"Article":[],"Course":[],"Dataset":[],"FAQPage":[],"Movie":[],"Person":[],"Product":[],"ProductReview":[],"Car":[],"Recipe":[],"Service":[],"SoftwareApplication":[],"WebPage":[]},"graphName":"","isEnabled":true},"graphs":[]},"schema_type":null,"schema_type_options":null,"pillar_content":false,"robots_default":true,"robots_noindex":false,"robots_noarchive":false,"robots_nosnippet":false,"robots_nofollow":false,"robots_noimageindex":false,"robots_noodp":false,"robots_notranslate":false,"robots_max_snippet":null,"robots_max_videopreview":null,"robots_max_imagepreview":"large","priority":null,"frequency":null,"local_seo":null,"seo_analyzer_scan_date":null,"breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-02-28 19:44:26","updated":"2026-02-09 17:28:53"},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/de\/wp-json\/wp\/v2\/posts\/55407","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/de\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/de\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/de\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/de\/wp-json\/wp\/v2\/comments?post=55407"}],"version-history":[{"count":1,"href":"https:\/\/prohoster.info\/de\/wp-json\/wp\/v2\/posts\/55407\/revisions"}],"predecessor-version":[{"id":159518,"href":"https:\/\/prohoster.info\/de\/wp-json\/wp\/v2\/posts\/55407\/revisions\/159518"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/de\/wp-json\/wp\/v2\/media?parent=55407"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/de\/wp-json\/wp\/v2\/categories?post=55407"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/de\/wp-json\/wp\/v2\/tags?post=55407"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}