Uploaded image for project: 'Traffic Server'
  1. Traffic Server
  2. TS-3440

Connect_retries re-connects even if request made it to origin

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Duplicate
    • None
    • 6.0.0
    • None
    • None

    Description

      While trying to workaround TS-3439 I decided to test out the connect retries option. During testing I found a case where it should not retry where it is.

      The scenario is as follows:

      • ATS makes a connection to an origin
      • the origin acks the entire request
      • the origin starts to send back a response (lets say first line of the header)
      • the origin sends an RST

      In this scenario ATS will re-connect to the origin, which is bad since we have already sent the request (and we aren't sure if the URL is re-entrant).

      Test case: https://github.com/jacksontj/trafficserver/commit/28059ccb93f9fb173792aeebf90062882dfdf9d5#diff-06f9ddbe6cc45d76ebb2cb21479dc805R182

      Attachments

        Issue Links

          breaks

          Bug - A problem which impairs or prevents the functions of the product. TS-3776 traffic_server failed assert `s->current.server->had_connect_fail()`

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. TS-3795 Invalid assertion in handle_server_connection_not_open

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed
          relates to

          Bug - A problem which impairs or prevents the functions of the product. TS-4328 Connect_retries re-connects even if request made it to origin (TS-3440 repeat)

          • Major - Major loss of function.
          • Closed

          Activity

            People

              jacksontj Thomas Jackson
              jacksontj Thomas Jackson
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: