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

Server Proxy Protocol Support

Details

    • 10.3.1-1, 10.3.1-2

    Description

      Attachments

        Issue Links

          duplicates

          New Feature - A new feature of the product, which has yet to be developed. MXS-381 support for transparent proxy

          • Major - Major loss of function.
          • Closed
          links to

          Web Link The PROXY protocol specs

          Activity

            Descending order - Click to sort in ascending order
            wlad Vladislav Vaintroub added a comment - - edited

            I did not use Percona implementation, but kept server parameter proxy_protocol_networks compatible to Percona.
            I believe our implementation does not have bugs mentioned in https://bugs.launchpad.net/percona-server/+bugs?field.tag=proxy-protocol . In addition, it is also tested with mtr

            the patch is there https://github.com/MariaDB/server/tree/bb-10.3-proxy-protocol

            wlad Vladislav Vaintroub added a comment - - edited I did not use Percona implementation, but kept server parameter proxy_protocol_networks compatible to Percona. I believe our implementation does not have bugs mentioned in https://bugs.launchpad.net/percona-server/+bugs?field.tag=proxy-protocol . In addition, it is also tested with mtr the patch is there https://github.com/MariaDB/server/tree/bb-10.3-proxy-protocol
            serg Sergei Golubchik added a comment -

            Thanks, laurynas!

            serg Sergei Golubchik added a comment - Thanks, laurynas !
            laurynas Laurynas Biveinis added a comment -

            If you merge Percona Server implementation, consider reviewing https://bugs.launchpad.net/percona-server/+bugs?field.tag=proxy-protocol

            laurynas Laurynas Biveinis added a comment - If you merge Percona Server implementation, consider reviewing https://bugs.launchpad.net/percona-server/+bugs?field.tag=proxy-protocol
            danblack Daniel Black added a comment -

            interesting. I'd probably give this its own TCP port and vio->type to be checked in vio_peer_addr for avoiding complexity in the other cases.

            Seem ssl client auth could be done also based on v2 metadata.

            danblack Daniel Black added a comment - interesting. I'd probably give this its own TCP port and vio->type to be checked in vio_peer_addr for avoiding complexity in the other cases. Seem ssl client auth could be done also based on v2 metadata.
            dshjoshi Dipti Joshi (Inactive) added a comment -

            This will help integration with MaxScale as well.

            dshjoshi Dipti Joshi (Inactive) added a comment - This will help integration with MaxScale as well.

            People

              wlad Vladislav Vaintroub
              stephane@skysql.com VAROQUI Stephane
              Votes:
              9 Vote for this issue
              Watchers:
              14 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Git Integration

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