From: Thomas Skinner <thomas@atskinner.net>
To: pve-devel@lists.proxmox.com
Cc: Thomas Skinner <thomas@atskinner.net>
Subject: [pve-devel] [PATCH SERIES manager/http-server/docs v2 0/3] fix #5699: add support for real IP
Date: Wed, 11 Dec 2024 21:27:03 -0600 [thread overview]
Message-ID: <20241212032706.151121-1-thomas@atskinner.net> (raw)
This v2 patch series continues adding support for setting a HTTP header for passing through a client IP
address for logging purposes.
Changes since v1:
* fixed styling issues
* renamed fields to clearer, more appropriate names
* adjusted logging format back to previous, made option opt-in
pve-docs:
Thomas Skinner (1):
fix #5699: pveproxy: add docs for real IP support
pveproxy.adoc | 29 +++++++++++++++++++++++++++++
1 file changed, 29 insertions(+)
pve-http-server:
Thomas Skinner (1):
fix #5699: pveproxy: add library methods for real IP support
src/PVE/APIServer/AnyEvent.pm | 38 ++++++++++++++++++++++++++++++++++-
src/PVE/APIServer/Utils.pm | 15 ++++++++++++++
2 files changed, 52 insertions(+), 1 deletion(-)
pve-manager:
Thomas Skinner (1):
fix #5699: pveproxy: add settings for real IP support
PVE/Service/pveproxy.pm | 2 ++
1 file changed, 2 insertions(+)
--
2.39.5
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next reply other threads:[~2024-12-12 3:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-12 3:27 Thomas Skinner [this message]
2024-12-12 3:27 ` [pve-devel] [PATCH docs v2 1/3] fix #5699: pveproxy: add docs for real IP support Thomas Skinner
2024-12-12 3:27 ` [pve-devel] [PATCH http-server v2 2/3] fix #5699: pveproxy: add library methods " Thomas Skinner
2024-12-12 3:27 ` [pve-devel] [PATCH manager v2 3/3] fix #5699: pveproxy: add settings " Thomas Skinner
2025-01-24 8:53 ` [pve-devel] applied-series: [PATCH SERIES manager/http-server/docs v2 0/3] fix #5699: add support for real IP Fabian Grünbichler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20241212032706.151121-1-thomas@atskinner.net \
--to=thomas@atskinner.net \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.