Server

When checking a request's remoteAddress, it's usually the address from which NIO received the request. While that's technically correct, Vapor servers are often hosted behind a reverse-proxy such as nginx. Therefore the original peer's address is often lost. To resolve this, it's not uncommon to set the original peer's address in a header such as X-Forwarded-For.

**Describe the solution you

The upstream issues got closed. It is referenced in:

• client/manager_test_helpers.go#L235

This issue was created by the ORY Closed Reference Notifier GitHub action.

This is a feature request, to display the valid SSL name (from the certificate) when starting up the server.

Steps to reproduce the issue, if applicable. Include the actual command and output and/or stack trace.

$ http-server -S

Starting up http-server, serving ./ through https
Available on:
  https://127.0.0.1:8080
  https://192.168.77.123:8080

**What did you exp

G1_FLAG_BMP has the wrong name its the inverse of its name it is used to indicate that the sprite has transparency and will require blending with the background to produce the end result. The vast majority of images have this flag set.

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!

[05:02:58] [INFO] Loaded ./resources/Scripts/Scene/35732/scene35732.lua
[05:02:58] [INFO] Loaded ./resources/Scripts/Scene/35732/scene35732_block35732.lua
[05:02:59] [INFO] Loaded ./resources/Scripts/Scene/35732/scene35732_group235732001.lua
[05:02:59] [INFO] Loaded ./resources/Scripts/Scene/35732/scene35732_group235732002.lua
[05:02:59] [INFO] Loaded ./resources/Scripts/Scene/35732/scene35732

Description

When using a client >= 1.4 but a server < 1.4, when editing a channel's ACLs, the client will offer to set the Listen ACL. However, as the server doesn't know of this ACL this obviously doesn't make sense.

From the user's perspective this will appear as if the Listen ACL was broken and that the server just won't remember what they configured the Listen ACL to (as the server