enforce ismaster responses have ok:1 before negotiating protocol

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Major - P3
    • 3.2.13, 3.3.9
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • ALL
    • v3.2
    • Platforms 16 (06/24/16)
    • 0
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      An interrupted isMaster response, e.g.

      { ok: 0.0, errmsg: "operation was interrupted", code: 11602 }

      results in a parsed protocol version of opQueryOnly.

      We need to verify that the ismaster response is ok before negotiating protocols, both in dbclient and network interface asio auth.

              Assignee:
              Matt Cotter (Inactive)
              Reporter:
              Matt Cotter (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: