Hi,
From url "https://www.openssl.org/docs/manmaster/man3/SSL_CTX_set1_chain_cert_store.html " I only found set function for chain_store. Will openssl add a get chain_store function? Or why didn't add the get function?

Thanks for this amazing tool!

The issue is as following:
If there are two virtual hosts (Server blocks) serving two host names or subdomains:

sd1.domain.com
sd2.domain.com

When the configuration is generated using the nginxconfig and if HTTP to HTTPS redirect is enabled following server block gets generated for each host:

--- For virtual host 1
# HTTP redirect
server {
  

Context and Description

The READMEs and any example code in all projects should be updated to reflect the move from the IBM-Swift organization to the Kitura organization.

If anyone wants to take on all or part of this, please comment here so other's know what you're working on and submit PR's. :-)

Thanks!

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.

Description

• Type: Bug
• Priority: Minor

Bug

There are multiple warnings raised in the process of building armcc in all.sh, but the test script does not treat them as errors.
Examples:

"ecp.c", line 175: Warning:  #188-D: enumerated type mixed with another type
      const mbedtls_md_type_t md_type = mbedtls_md_list()[0];
                                        ^
"psa_crypt

Expected Behavior

If cookie-expire is setted to long period (1 week) and cookie-refresh to 1 hour (because Google's JWT is valid 1 hour), oauth2-proxy should refresh session cookie earliest after first hour and if successfully recieve access token (JWT) oauth2-proxy should do next cookie refresh earliest after one hour (a