Server does not enforce handshake protocol requirement that 'application.name' be present if the client metadata defines an 'application' section

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Works as Designed
    • Priority: Major - P3
    • None
    • Affects Version/s: 3.6.0
    • Component/s: Internal Code
    • None
    • ALL
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Per the handshake protocol spec, we require that if the optional 'application' section is specified in the metadata passed by the driver to the server, then the 'name' subfield must be specified (and presumably non-empty). Currently, client_metadata.cpp does not enforce this requirement; it only checks that the 'name' field is of type string if present.

            Assignee:
            Mark Benvenuto
            Reporter:
            Bernard Gorman
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: