nginx
nginx is an HTTP and reverse proxy server, a mail proxy server, and a generic TCP/UDP proxy server. Nginx was written with an explicit goal of provide high performance on sites with high traffic, so it can be used as a reverse proxy, load balancer and HTTP cache.
Here are 8,892 public repositories matching this topic...
-
Updated
Dec 21, 2021 - Python
-
Updated
Dec 16, 2021 - JavaScript
-
Updated
Dec 25, 2021 - C
-
Updated
Oct 20, 2021 - Shell
custom errors image needs to be promoted.
Steps:
- Open a PR for https://github.com/kubernetes/k8s.io/blob/main/k8s.gcr.io/images/k8s-staging-ingress-nginx/images.yaml#L129, add a new line below this one with the following:
"sha256:1d69f28d6412b0f2a6302f9df9a6bc49e83703336a35f95ab109cad10e039120": ["1.0.0"]
- Once this PR gets merged, open a new PR in ingress-nginx repo to updat
-
Updated
Dec 29, 2021 - Go
-
Updated
Nov 21, 2021
Discussed in apache/apisix#5892
Originally posted by lrfdehao December 23, 2021
Suppose I have two fields, include_resp_body as the switch, resp_limit_size as the limit size. After configuring these two parameters, if resp_body exceeds the size of resp_limit_size, resp_body will not be recorded in the log
-
Updated
Nov 18, 2021 - TypeScript
-
Updated
Dec 29, 2021 - JavaScript
-
Updated
Dec 29, 2021 - C++
-
Updated
Jul 18, 2019
-
Updated
Dec 28, 2021 - Shell
-
Updated
Sep 25, 2021 - Python
I use naxsi with nginx. I want to add request id which is used by nginx to nginx error logs when blocked by naxsi. Is it possible ? Thanks for help.
-
Updated
Nov 7, 2021 - PHP
-
Updated
Dec 29, 2021 - Go
Describe the bug
There is a bug in podinfo chart which will not deploy service if you enabled canary, even though you enabled service via helm values.
https://github.com/fluxcd/flagger/blob/main/charts/podinfo/templates/service.yaml#L1
To Reproduce
If you set values like this, it will not deploy service.
service:
enabled: true # service will not be deployed if ca-
Updated
Dec 23, 2021 - Python
-
Updated
Dec 16, 2021 - Jinja
-
Updated
Aug 27, 2021 - C
Created by Igor Sysoev
Released October 4, 2004
- Repository
- nginx/nginx
- Website
- nginx.org
- Wikipedia
- Wikipedia
Is there an existing issue for this?
Kong version (
$ kong version)2.5.1.0
Current Behavior
When calling
kong.response.exit(), the function automatically sets the Content-Length header on the response even if the Transfer-Encoding header is present. This is in violation of RFC 7230 3.3.2: