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

APIcast times out when using a Forward Proxy a large body

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 2.9 GA
    • 2.5 GA, 2.5.1
    • Gateway
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • +
    • Hide

      1. Deploy Red Hat 3scale 2.5 On-premises in OpenShift and using a Forward Proxy.

      2. Create a new Service called "proxy-test" using the default 'user_key' authentication.

      3. Create a new Application Plan and Application for the Service and configure its Backend API with the Echo API.

      4. Add the Mapping Rule "POST /" and update the Staging configuration.

      5. Set the variables 'HTTP_PROXY', 'HTTPS_PROXY' and 'NO_PROXY' accordingly on the 'apicast-staging' pod.

      6. Perform a call with 1k, 5, 10k.

      Expected: All calls should work.

      Scenario: The request returns 504 Gateway Timeout

      Show
      1. Deploy Red Hat 3scale 2.5 On-premises in OpenShift and using a Forward Proxy. 2. Create a new Service called "proxy-test" using the default 'user_key' authentication. 3. Create a new Application Plan and Application for the Service and configure its Backend API with the Echo API. 4. Add the Mapping Rule "POST /" and update the Staging configuration. 5. Set the variables 'HTTP_PROXY', 'HTTPS_PROXY' and 'NO_PROXY' accordingly on the 'apicast-staging' pod. 6. Perform a call with 1k, 5, 10k. Expected: All calls should work. Scenario: The request returns 504 Gateway Timeout

      Please check the Steps to Reproduce.

      The Red Hat 3scale Support team has been able to replicate the issue internally.

      I'm attaching the relevant data from my own local instance on both files 'success_call.txt' and 'failure_call.txt'.

      Values between 40k and 50k might either work or not.

      NOTE: When not using a forward proxy, the 50k body call works in less than one second.

        1. failure_call.txt
          107 kB
        2. success_call.txt
          106 kB
        3. failure-26-27
          31 kB

          1.
          		 prepare tests multiple payloads Sub-task Closed Major Unassigned

              Unassigned Unassigned
              rhn-support-ekonecsn Estevao Konecsni
              Jakub Smadis Jakub Smadis (Inactive)
              Eloy Coto Eloy Coto (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: