Uploaded image for project: 'Hybrid Cloud Console'
  1. Hybrid Cloud Console
  2. RHCLOUD-33532

Turnpike | Backend config path matching

XMLWordPrintable

    • Quality / Stability / Reliability
    • 5
    • False
    • Hide

      None

      Show
      None
    • False
    • None
    • Unset
    • No
    • 3
    • Access & Management Sprint 109, Access & Management Sprint 110, Access & Management Sprint 111, A&M Tech Debt Sprint Q2 2025, Access & Management Sprint 112, Access & Management Sprint 113, Access & Management Sprint 114, A&M Tech Debt Sprint Q3 2025, Access & Management Sprint 115, Access & Management Sprint 116, Access & Management Sprint 117

      The logs might be confusing for the actual backend matched, cause it is only for auth:
      https://github.com/RedHatInsights/turnpike/blob/master/turnpike/views.py#L25

      But not the same for the actual origin that's forwarded. https://github.com/RedHatInsights/turnpike/blob/master/nginx/backend_template.conf.j2#L1
      The backend generation would add wildcard
      for example if we have two paths defined in the backend
      /api/pulp

      /api/pulp-content

      would become /api/pulp* /api/pulp-content*

      requests to /api/pulp-content/default might be routed to /api/pulp*

      We have to keep this in mind or find a solution for this situation

              mbarcina@redhat.com Mikel Barcina
              rh-ee-zhzeng Jay Zeng
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: