Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-24595

enforce ismaster responses have ok:1 before negotiating protocol

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 3.2.13, 3.3.9
    • None
    • None
    • Fully Compatible
    • ALL
    • v3.2
    • Platforms 16 (06/24/16)
    • 0

    Description

      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.

      Attachments

        Activity

          People

            matt.cotter Matt Cotter
            matt.cotter Matt Cotter
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: