Skip to content

Commit 080890c

Browse files
webcppwebcpp
committed
update nginx to v1.27.2
1 parent 7b8722c commit 080890c

24 files changed

+2117
-488
lines changed

‎CHANGES

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,24 @@
11

2+
Changes with nginx 1.27.2 02 Oct 2024
3+
4+
*) Feature: SSL certificates, secret keys, and CRLs are now cached on
5+
start or during reconfiguration.
6+
7+
*) Feature: client certificate validation with OCSP in the stream
8+
module.
9+
10+
*) Feature: OCSP stapling support in the stream module.
11+
12+
*) Feature: the "proxy_pass_trailers" directive in the
13+
ngx_http_proxy_module.
14+
15+
*) Feature: the "ssl_client_certificate" directive now supports
16+
certificates with auxiliary information.
17+
18+
*) Change: now the "ssl_client_certificate" directive is not required
19+
for client SSL certificates verification.
20+
21+
222
Changes with nginx 1.27.1 14 Aug 2024
323

424
*) Security: processing of a specially crafted mp4 file by the

‎CHANGES.ru

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,24 @@
11

2+
Изменения в nginx 1.27.2 02.10.2024
3+
4+
*) Добавление: SSL-сертификаты, секретные ключи и списки CRL теперь
5+
кешируются на старте или во время переконфигурации.
6+
7+
*) Добавление: проверка клиентских сертификатов с помощью OCSP в модуле
8+
stream.
9+
10+
*) Добавление: поддержка OCSP stapling в модуле stream.
11+
12+
*) Добавление: директива proxy_pass_trailers в модуле
13+
ngx_http_proxy_module.
14+
15+
*) Добавление: директива ssl_client_certificate теперь поддерживает
16+
сертификаты с дополнительными данными.
17+
18+
*) Изменение: теперь наличие директивы ssl_client_certificate не
19+
обязательно для проверки клиентских SSL-сертификатов.
20+
21+
222
Изменения в nginx 1.27.1 14.08.2024
323

424
*) Безопасность: обработка специально созданного mp4-файла модулем

‎CODE_OF_CONDUCT.md

Lines changed: 126 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,126 @@
1+
# Contributor Covenant Code of Conduct
2+
3+
## Our Pledge
4+
5+
We as members, contributors, and leaders pledge to make participation in our
6+
community a harassment-free experience for everyone, regardless of age, body
7+
size, visible or invisible disability, ethnicity, sex characteristics, gender
8+
identity and expression, level of experience, education, socio economic status,
9+
nationality, personal appearance, race, caste, color, religion, or sexual
10+
identity and orientation.
11+
12+
We pledge to act and interact in ways that contribute to an open, welcoming,
13+
diverse, inclusive, and healthy community.
14+
15+
## Our Standards
16+
17+
Examples of behavior that contributes to a positive environment for our
18+
community include:
19+
20+
- Demonstrating empathy and kindness toward other people
21+
- Being respectful of differing opinions, viewpoints, and experiences
22+
- Giving and gracefully accepting constructive feedback
23+
- Accepting responsibility and apologizing to those affected by our mistakes
24+
and learning from the experience
25+
- Focusing on what is best not just for us as individuals, but for the
26+
overall community
27+
28+
Examples of unacceptable behavior include:
29+
30+
- The use of sexualized language or imagery, and sexual attention or advances
31+
of any kind
32+
- Trolling, insulting or derogatory comments, and personal or political attacks
33+
- Public or private harassment
34+
- Publishing others' private information, such as a physical or email address,
35+
without their explicit permission
36+
- Other conduct which could reasonably be considered inappropriate in a
37+
professional setting
38+
39+
## Enforcement Responsibilities
40+
41+
Community leaders are responsible for clarifying and enforcing our standards
42+
of acceptable behavior and will take appropriate and fair corrective action
43+
in response to any behavior that they deem inappropriate, threatening,
44+
offensive, or harmful.
45+
46+
Community leaders have the right and responsibility to remove, edit, or reject
47+
comments, commits, code, wiki edits, issues, and other contributions that are
48+
not aligned to this Code of Conduct, and will communicate reasons for
49+
moderation decisions when appropriate.
50+
51+
## Scope
52+
53+
This Code of Conduct applies within all community spaces, and also applies when
54+
an individual is officially representing the community in public spaces.
55+
Examples of representing our community include using an official email address,
56+
posting via an official social media account, or acting as an appointed
57+
representative at an online or offline event.
58+
59+
## Enforcement
60+
61+
Instances of abusive, harassing, or otherwise unacceptable behavior may be
62+
reported to the community leaders responsible for enforcement at
63+
<nginx-oss-community@f5.com>. All complaints will be reviewed and investigated
64+
promptly and fairly.
65+
66+
All community leaders are obligated to respect the privacy and security of the
67+
reporter of any incident.
68+
69+
## Enforcement Guidelines
70+
71+
Community leaders will follow these Community Impact Guidelines in determining
72+
the consequences for any action they deem in violation of this Code of Conduct:
73+
74+
### 1. Correction
75+
76+
**Community Impact**: Use of inappropriate language or other behavior deemed
77+
unprofessional or unwelcome in the community.
78+
79+
**Consequence**: A private, written warning from community leaders, providing
80+
clarity around the nature of the violation and an explanation of why the
81+
behavior was inappropriate. A public apology may be requested.
82+
83+
### 2. Warning
84+
85+
**Community Impact**: A violation through a single incident or series of actions.
86+
87+
**Consequence**: A warning with consequences for continued behavior. No
88+
interaction with the people involved, including unsolicited interaction with
89+
those enforcing the Code of Conduct, for a specified period of time. This
90+
includes avoiding interactions in community spaces as well as external
91+
channels like social media. Violating these terms may lead to a temporary or
92+
permanent ban.
93+
94+
### 3. Temporary Ban
95+
96+
**Community Impact**: A serious violation of community standards, including
97+
sustained inappropriate behavior.
98+
99+
**Consequence**: A temporary ban from any sort of interaction or public
100+
communication with the community for a specified period of time. No public or
101+
private interaction with the people involved, including unsolicited interaction
102+
with those enforcing the Code of Conduct, is allowed during this period.
103+
Violating these terms may lead to a permanent ban.
104+
105+
### 4. Permanent Ban
106+
107+
**Community Impact**: Demonstrating a pattern of violation of community
108+
standards, including sustained inappropriate behavior, harassment of an
109+
individual, or aggression toward or disparagement of classes of individuals.
110+
111+
**Consequence**: A permanent ban from any sort of public interaction within
112+
the community.
113+
114+
## Attribution
115+
116+
This Code of Conduct is adapted from the
117+
[Contributor Covenant](https://www.contributor-covenant.org), version 2.1,
118+
available at
119+
<https://www.contributor-covenant.org/version/2/1/code_of_conduct.html>.
120+
121+
Community Impact Guidelines were inspired by
122+
[Mozilla's code of conduct enforcement ladder](https://github.com/mozilla/inclusion).
123+
124+
For answers to common questions about this code of conduct, see the FAQ at
125+
<https://www.contributor-covenant.org/faq>. Translations are available at
126+
<https://www.contributor-covenant.org/translations>.

‎CONTRIBUTING.md

Lines changed: 110 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,110 @@
1+
# Contributing Guidelines
2+
3+
The following is a set of guidelines for contributing to nginx project.
4+
We really appreciate that you are considering contributing!
5+
6+
## Table of Contents
7+
8+
- [Ask a Question](#ask-a-question)
9+
- [Report a Bug](#report-a-bug)
10+
- [Suggest a Feature or Enhancement](#suggest-a-feature-or-enhancement)
11+
- [Open a Discussion](#open-a-discussion)
12+
- [Submit a Pull Request](#submit-a-pull-request)
13+
- [Issue Lifecycle](#issue-lifecycle)
14+
15+
## Ask a Question
16+
17+
To ask a question, open an issue on GitHub with the label `question`.
18+
19+
## Report a Bug
20+
21+
To report a bug, open an issue on GitHub with the label `bug` using the
22+
available bug report issue template. Before reporting a bug, make sure the
23+
issue has not already been reported.
24+
25+
## Suggest a Feature or Enhancement
26+
27+
To suggest a feature or enhancement, open an issue on GitHub with the label
28+
`feature` or `enhancement` using the available feature request issue template.
29+
Please ensure the feature or enhancement has not already been suggested.
30+
31+
## Open a Discussion
32+
33+
If you want to engage in a conversation with the community and maintainers,
34+
we encourage you to use
35+
[GitHub Discussions](https://github.com/nginx/nginx/discussions).
36+
37+
## Submit a Pull Request
38+
39+
Follow this plan to contribute a change to NGINX source code:
40+
41+
- Fork the NGINX repository
42+
- Create a branch
43+
- Implement your changes in this branch
44+
- Submit a pull request (PR) when your changes are tested and ready for review
45+
46+
Refer to
47+
[NGINX Development Guide](https://nginx.org/en/docs/dev/development_guide.html)
48+
for questions about NGINX programming.
49+
50+
### Formatting Changes
51+
52+
- Changes should be formatted according to the
53+
[code style](https://nginx.org/en/docs/dev/development_guide.html#code_style)
54+
used by NGINX; sometimes, there is no clear rule, in which case examine how
55+
existing NGINX sources are formatted and mimic this style; changes will more
56+
likely be accepted if style corresponds to the surrounding code
57+
58+
- Keep a clean, concise and meaningful commit history on your branch, rebasing
59+
locally and breaking changes logically into commits before submitting a PR
60+
61+
- Each commit message should have a single-line subject line followed by verbose
62+
description after an empty line
63+
64+
- Limit the subject line to 67 characters, and the rest of the commit message
65+
to 76 characters
66+
67+
- Use subject line prefixes for commits that affect a specific portion of the
68+
code; examples include "Upstream:", "QUIC:", or "Core:"; see the commit history
69+
to get an idea of the prefixes used
70+
71+
- Reference issues in the the subject line; if the commit fixes an issue,
72+
[name it](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue)
73+
accordingly
74+
75+
### Before Submitting
76+
77+
- The proposed changes should work properly on a wide range of
78+
[supported platforms](https://nginx.org/en/index.html#tested_os_and_platforms)
79+
80+
- Try to make it clear why the suggested change is needed, and provide a use
81+
case, if possible
82+
83+
- Passing your changes through the test suite is a good way to ensure that they
84+
do not cause a regression; the repository with tests can be cloned with the
85+
following command:
86+
87+
```bash
88+
git clone https://github.com/nginx/nginx-tests.git
89+
```
90+
91+
- Submitting a change implies granting project a permission to use it under the
92+
[BSD-2-Clause license](https://github.com/nginx/nginx/blob/master/LICENSE)
93+
94+
## Issue Lifecycle
95+
96+
To ensure a balance between work carried out by the NGINX engineering team
97+
while encouraging community involvement on this project, we use the following
98+
issue lifecycle:
99+
100+
- A new issue is created by a community member
101+
102+
- An owner on the NGINX engineering team is assigned to the issue; this
103+
owner shepherds the issue through the subsequent stages in the issue lifecycle
104+
105+
- The owner assigns one or more
106+
[labels](https://github.com/nginx/nginx/issues/labels) to the issue
107+
108+
- The owner, in collaboration with the wider team (product management and
109+
engineering), determines what milestone to attach to an issue;
110+
generally, milestones correspond to product releases

‎LICENSE

Lines changed: 24 additions & 26 deletions
Original file line numberDiff line numberDiff line change
@@ -1,26 +1,24 @@
1-
/*
2-
* Copyright (C) 2002-2021 Igor Sysoev
3-
* Copyright (C) 2011-2024 Nginx, Inc.
4-
* All rights reserved.
5-
*
6-
* Redistribution and use in source and binary forms, with or without
7-
* modification, are permitted provided that the following conditions
8-
* are met:
9-
* 1. Redistributions of source code must retain the above copyright
10-
* notice, this list of conditions and the following disclaimer.
11-
* 2. Redistributions in binary form must reproduce the above copyright
12-
* notice, this list of conditions and the following disclaimer in the
13-
* documentation and/or other materials provided with the distribution.
14-
*
15-
* THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND
16-
* ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
17-
* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
18-
* ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
19-
* FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
20-
* DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
21-
* OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
22-
* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
23-
* LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
24-
* OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
25-
* SUCH DAMAGE.
26-
*/
1+
Copyright (C) 2002-2021 Igor Sysoev
2+
Copyright (C) 2011-2024 Nginx, Inc.
3+
All rights reserved.
4+
5+
Redistribution and use in source and binary forms, with or without
6+
modification, are permitted provided that the following conditions
7+
are met:
8+
1. Redistributions of source code must retain the above copyright
9+
notice, this list of conditions and the following disclaimer.
10+
2. Redistributions in binary form must reproduce the above copyright
11+
notice, this list of conditions and the following disclaimer in the
12+
documentation and/or other materials provided with the distribution.
13+
14+
THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND
15+
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
16+
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
17+
ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
18+
FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
19+
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
20+
OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
21+
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
22+
LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
23+
OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
24+
SUCH DAMAGE.

0 commit comments

Comments
 (0)