# HG changeset patch
# User Sergey Kandaurov <pluknet@nginx.com>
# Date 1587114105 -10800
# Node ID de715cdd425723bbdd9f532645a8595323999a7d
# Parent  76e8ec502c69834322fc3a1aff528342e7f3367b
Revert "Rejecting new connections with non-zero Initial packet."

chrome-unstable 83.0.4103.7 starts with Initial packet number 1.

I couldn't find a proper explanation besides this text in quic-transport:
    An endpoint MAY skip packet numbers when sending
    packets to detect this (Optimistic ACK Attack) behavior.

diff --git a/src/event/ngx_event_quic.c b/src/event/ngx_event_quic.c
--- a/src/event/ngx_event_quic.c
+++ b/src/event/ngx_event_quic.c
@@ -583,12 +583,6 @@ ngx_quic_new_connection(ngx_connection_t
         return NGX_ERROR;
     }
 
-    if (pkt->pn != 0) {
-        ngx_log_error(NGX_LOG_INFO, c->log, 0,
-                      "invalid initial packet number %L", pkt->pn);
-        return NGX_ERROR;
-    }
-
     if (ngx_quic_init_connection(c) != NGX_OK) {
         return NGX_ERROR;
     }