Uploaded image for project: 'Undertow'
  1. Undertow
  2. UNDERTOW-1459

ProxyHandler returns status code 503 instead of 504

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Minor
    • 2.2.13.Final, 2.0.42.Final
    • 2.0.16.Final
    • Proxy
    • None

    Description

      According to the HTTP status codes docs, a server that's acting as a gateway or proxy and did not receive a timely response from the upstream server should return status code 504 Gateway Timeout, currently the class io.undertow.server.handlers.proxy.ProxyHandler returns 503 Service Unavailable.

      Attachments

        Issue Links

          causes

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-22753 (7.4.z) Status Code in ReverseProxyTestCase should be 504

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Verified

          Bug - A problem that impairs or prevents the functions of the product. WFLY-15714 Status Code in ReverseProxyTestCase should be 504

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              rhn-cservice-bbaranow Bartosz Baranowski
              lehphyro Leandro Aparecido (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: