Custom Query (2297 matches)
Results (70 - 72 of 2297)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#2519 | invalid | Support for QUIC and HTTP3 | ||
Description |
Hi, Can we get a ballpark ETA on when these features will be out of the preview as we are trying to implement the same in our application? We have tried patch versions of this but we were not able to achieve the same because of the lack of official support and documentation on the same. Reporting the same here as we have not found an issues tracker in the GitHub repository. Reference: https://www.nginx.com/blog/binary-packages-for-preview-nginx-quic-http3-implementation/ |
|||
#2518 | duplicate | if in location with regex capture will reset numeric variable like $1 from captured group but not for named capture group | ||
Description |
This works: location ~ /uploads/(?<filePath>.*)$ { if ($http_referer !~ "^https://example.com") { return 403; } more_set_headers 'X-Path: $1' 'X-Path2: $filePath' 'X-Referer: $http_referer'; try_files $uri altUploads/$filePath ../otherUploads/$filePath =404; } and this won't: location ~ /uploads/(.*)$ { if ($http_referer !~ "^https://example.com") { return 403; } more_set_headers 'X-Path: $1' 'X-Referer: $http_referer'; try_files $uri altUploads/$1 ../otherUploads/$1 =404; }
The location ~ /uploads/(.*)$ { more_set_headers 'X-Path: $1' 'X-Referer: $http_referer'; try_files $uri altUploads/$1 ../otherUploads/$1 =404; } |
|||
#2517 | invalid | QUIC:After sending a RESET_STREAM, nginx does not cease transmission of STREAM frames? | ||
Description |
RFC 9000, 19.4 has a related statement about RESET_STREAM frame. After sending a RESET_STREAM, an endpoint ceases transmission and retransmission of STREAM frames on the identified stream. A receiver of RESET_STREAM can discard any data that it already received on that stream.
I found the logic to cease the retransmission of STREAM frames in
When sending a stream frame, was also to cease transmission of STREAM frames in |