Uploaded image for project: 'Dev - Nexus Repo'
  1. Dev - Nexus Repo
  2. NEXUS-8930

outbound http connections may be immediately closed on 304 response with ETAG instead of pooled

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.11.3
    • Fix Version/s: 2.11.4
    • Component/s: Repository
    • Labels:
    • Story Points:
      1
    • Sprint:
      Sprint 46

      Description

      This affects latest NX2 it seems. NX2 claims it will keep alive the connection (default with HTTP/1.1) and even ensures it with a header if client is HTTP/1.0 (as with that protocol level extra header Connection: keep-alive is needed), but then immediately drops connection on response is sent. This leaves no chance for connection pooling clients (like NX2/NX3, unlike Wagons) to properly handle connections, as connections returned to pool and believed to be alive will be actually immediately closed.

      OOTB Jetty 8 does not do this, this has to be something in NX2.

      Either fix the
      a) connection to remain alive if said so, or
      b) as simpler fix just add "Connection: close" header when client is HTTP/1.1 and prevent addition of (done by Jetty) "Connection: keep-alive" header when client is HTTP/1.0

      Marked as affects 2.11.3, but it might affect other 2.x versions too.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              mprescott Michael Prescott
              Reporter:
              cstamas Tamás Cservenák
              Last Updated By:
              Peter Lynch
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Date of First Response:

                  tigCommentSecurity.panel-title