• Recent
    • Tags
    • Popular
    • Register
    • Login

    Please Note This forum exists for community support for the Mango product family and the Radix IoT Platform. Although Radix IoT employees participate in this forum from time to time, there is no guarantee of a response to anything posted here, nor can Radix IoT, LLC guarantee the accuracy of any information expressed or conveyed. Specific project questions from customers with active support contracts are asked to send requests to support@radixiot.com.

    Radix IoT Website Mango 3 Documentation Website Mango 4 Documentation Website Mango 5 Documentation Website

    Logging HTTP publisher

    User help
    2
    5
    1.1k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • P
      psysak
      last edited by

      I'd like to log exactly what the HTTP publisher is sending out to the server that it's connecting to. Is there a way to do this?

      1 Reply Last reply Reply Quote 0
      • P
        psysak
        last edited by

        I just answered my own question. Netcat -l -p whatever port and point the HTTP publisher to localhost:whateverport. Done :)

        1 Reply Last reply Reply Quote 0
        • phildunlapP
          phildunlap
          last edited by

          Hi Psysak,

          Glad you figured it out. Here's a past thread with info about this: https://forum.infiniteautomation.com/topic/2187/how-to-use-publishers-http-sender

          1 Reply Last reply Reply Quote 0
          • P
            psysak
            last edited by

            That's where I got the idea for netcat, figured I'd post the solution here cause that other thread was a little more complicated than what I wanted to do. Thanks Phil

            1 Reply Last reply Reply Quote 0
            • phildunlapP
              phildunlap
              last edited by

              Certainly! nc -l port# is definitely the TLDR of that thread :D

              1 Reply Last reply Reply Quote 0
              • First post
                Last post