Uploaded image for project: 'Red Hat 3scale API Management'
  1. Red Hat 3scale API Management
  2. THREESCALE-409

Wildcard router doesn't correctly pass headers with underscore in name

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Critical Critical
    • 2.2 ER1
    • 2.1 CR2
    • System
    • Hide

      Change all header names in all services so that there is no underscore in them.

      Show
      Change all header names in all services so that there is no underscore in them.
    • Hide
      • Deploy amp with WILDCARD_POLICY=Subdomain parameter
      • Create service authenticated with AppId and AppKey
      • Create application plan, and application pointing to new service
      • The test of service will fail with 403 status code
      Show
      Deploy amp with WILDCARD_POLICY=Subdomain parameter Create service authenticated with AppId and AppKey Create application plan, and application pointing to new service The test of service will fail with 403 status code

      When 3scale amp is configured with wildcard router, the headers, which name contains underscore, are passed neither to production nor to staging apicasts.

      Any request to service with header where is underscore fails with 403 status code and Authentication parameters missing. message.

      This issue affects services with AppId AppKey authentication, where header names for app_id and app_key contains underscores by default.

          1.
          		 Documentation of workaround for wildcard router headers Sub-task Closed Major Nathan Wilson (Inactive)

              Unassigned Unassigned
              mjaros@redhat.com Miroslav Jaroš (Inactive)
              Miroslav Jaroš Miroslav Jaroš (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: