Uploaded image for project: 'OpenShift Logging'
  1. OpenShift Logging
  2. LOG-7188

[release-6.2] When cluster-wide proxy configured where the proxy url contains user with encoded @, fails to log forward

XMLWordPrintable

    • Incidents & Support
    • False
    • Hide

      None

      Show
      None
    • False
    • NEW
    • NEW
    • Hide
      Before this update, configuring a cluster-wide proxy with a URL containing a username that included an encoded "@" symbol (e.g., "user%40name") caused log forwarding to fail. With this update, proxy configuration now correctly supports URL-encoded values, resolving the issue and allowing log forwarding to operate successfully in such configurations.
      Show
      Before this update, configuring a cluster-wide proxy with a URL containing a username that included an encoded "@" symbol (e.g., "user%40name") caused log forwarding to fail. With this update, proxy configuration now correctly supports URL-encoded values, resolving the issue and allowing log forwarding to operate successfully in such configurations.
    • Bug Fix
    • Log Collection - Sprint 270, Log Collection - Sprint 271
    • Moderate

      Description of problem:

      When it's configured a cluster-wide proxy where the proxy url is:

      https://userpart1%40userpart2:password@proxyurl.com

      The username "userpart1%40userpart2" is really "userpart1@userpart2", then, the Vector collector fails to deliver the logs to an output (Splunk) that needs to go through the proxy

      Version-Release number of selected component (if applicable):

      Logging 5.9.12
      Vector

      How reproducible:

      Always

      Steps to Reproduce:

      1. Deploy a cluster and configure cluster-wide proxy where the proxy url is https://userpart1%40userpart2:password@proxyurl.com
      2. Configure the Vector collector to log forward the logs to a Splunk instance that needs to go through the proxy

      Actual results:

      It fails to deliver the logs to the Splunk output

      Expected results:

      Able to log forward the logs to the Splunk output

      Additional info:

      The same failing for CloudWatch.

              vparfono Vitalii Parfonov
              rhn-support-ocasalsa Oscar Casal Sanchez
              Anping Li Anping Li
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: