Uploaded image for project: 'IoTivity'
  1. IoTivity
  2. IOT-1415

[CA] [TCP] /oic/ping resource is successfully registering and deregistering observe requests, even though it is shown as non observable resource in discovery response.

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Undecided
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: IoTivity 1.2.0
    • Component/s: SDK
    • Labels:
      None
    • Found in Version/s:
      1.2.0-RC3
    • Fixed in Version/s:
      IoTivity 1.2.0
    • Operating System:
      Ubuntu
    • Issue Severity:
      Major
    • Reproducibility:
      Always (100%)

      Description

      [Procedure]
      1. Build IoTivity with WITH_TCP=1 option
      2. Start a resource
      3. Start a client.
      4. Discover the resources
      5. Send a confirmable Observe request to the "/oic/ping" resource
      6. Send a confirmable cancel Observe request to the "/oic/ping" resource

      [Expected]
      5. /oic/ping resource should respond with Normal GET response(2.05), without any observe header option (ACK message)
      6. /oic/ping resource should respond with Normal GET response(2.05), without any observe header option (ACK message)

      [Actual]
      5. /oic/ping resource is responding with observe registered (Header Option = 0) (CON message)
      6. /oic/ping resource is responding with observe de-registered (Header Option = 1) (CON message)

        Attachments

        # Subject Branch Project Status CR V

          Activity

            People

            • Assignee:
              johyuna Hyuna Jo
              Reporter:
              i.mushfiq Mushfiqul Islam
            • Votes:
              0 Vote for this issue
              Watchers:
              11 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: