Opened 10 years ago

Closed 10 years ago

#1503 closed Bug (fixed)

tr-remote debug prints wrong rpc post & response data

Reported by: Waldorf Owned by: charles
Priority: Normal Milestone: 1.41
Component: Daemon Version: 1.40
Severity: Minor Keywords:
Cc:

Description

The tr-remote debug prints the data to POST as pre- and postfixed with square brackets, while if you try to feed the rpc with square brackets (through eg. CURL) you'll get an error 'method not found'.
Example:

posting [{
    "arguments": {
        "fields": [
            "files", 
            "name", 
            "priorities", 
            "wanted"
        ], 
        "ids": 70
    }, 
    "method": "torrent-get", 
    "tag": 2
}
]

Change History (6)

comment:1 Changed 10 years ago by Waldorf

*correction: the result returned is: "no method name".

comment:2 Changed 10 years ago by charles

  • Component changed from libtransmission to Daemon
  • Milestone changed from None Set to 1.41
  • Severity changed from Normal to Minor
  • Status changed from new to assigned

comment:3 Changed 10 years ago by charles

  • Keywords backport-candidate added
  • Milestone changed from 1.41 to 1.50
  • Resolution set to fixed
  • Status changed from assigned to closed

trunk: r7135

comment:4 Changed 10 years ago by charles

  • Keywords backport-candidate removed
  • Milestone changed from 1.50 to 1.41

1.4x: r7140

comment:5 Changed 10 years ago by Waldorf

  • Resolution fixed deleted
  • Status changed from closed to reopened
  • Summary changed from tr-remote debug prints wrong rpc post data to tr-remote debug prints wrong rpc post & response data

Charles, sorry to reopen this, but the same applies to the debug response data

comment:6 Changed 10 years ago by charles

  • Resolution set to fixed
  • Status changed from reopened to closed

trunk: r7145 1.4x: r7146

Note: See TracTickets for help on using tickets.