Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-29942

Provide insight on proxy_protocol usage

    XMLWordPrintable

Details

    • New Feature
    • Status: Open (View Workflow)
    • Major
    • Resolution: Unresolved
    • None
    • Protocol
    • None

    Description

      Currently when connecting via proxy protocol it just replaces the actual source address of the client connection with the address given in the PROXY protocol header.

      This is completely transparent to later server layers, but there may be circumstances where one might still want to know that proxy protocol was applied, or even want to be able to identify the actual proxy a connection came through (or at least the last one in the proxy chain).

      This could e.g. be accomplished by adding some new status variables like proxy_protocol_used and proxy_protocol_via.

      There should be only minimal overhead in populating the two at connect time.

      Attachments

        Activity

          People

            serg Sergei Golubchik
            hholzgra Hartmut Holzgraefe
            Votes:
            1 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:

              Git Integration

                Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.