tls

Three or four parameters of header_down use Regex, and one does simply overwriting.
Caddy did not simply make a case-sensitive distinction of the header key value when it overwrites it, but I experienced a case-sensitive distinction of the header key value when I used Regex.
I think it is not intended.

Reproduction of issue.

example.com {
        reverse_proxy {
                t

Right now in different places in the SE codebase there are references to /opt and then as well to /usr.

All SE code should reference one place only. Could someone please create a PR that fixes this.

This PR should also take PR #454 into consideration (no conflicts)

Is your feature request related to a problem? Please describe.

While less common, some users would like to set different passwords for the unlocking a Java keystore and the private key contained within.

Requested in jetstack/cert-manager#4186.

Describe the solution you'd like
Upgrade https://github.com/pavel-v-chernykh/keystore-go to v4.
Add support f

There's little information about what keys and values are in the output, what it means and how they are related to the screen output. In general that needs to be added. (special topics see #1675, #1674)

Problem:

A common pattern is:

GUARD(s2n_stuffer_skip_write(stuffer, bytes_to_write));
uint8_t* ptr = suffer->blob.data + stuffer->write_cursor - bytes_to_write;

which could be simplified.

Solution:

*ptr could be an *out parameter to s2n_stuffer_skip_write

• Does this change what S2N sends over the wire? No.
• Does this change any public APIs? No.

What would you like to be added

We can't query smallstep for anything related to certs because the only thing in the DB is the bytes of the cert. Storing the cert alongside more columns like the common name, not after date, and more, would let us enable more complex queries, and optimize performance for future use cases.

Why this is needed

Enable searching of Certificates signed by attrib

Suggested enhancement

The max_content_len (in and out) is configurable at compile time only. It is used in mbedtls_ssl_setup for alloc memory.

Justification

When in need of having 2 tls sessions to different servers, even if one server is not supporting max_content_len, both sessions are forced to have 16k of IN buffer since it is a compile time option. If configurable at run time,