View Issue Details

IDProjectCategoryView StatusLast Update
0003639Talerexchangepublic2015-03-24 17:57
ReporterChristian Grothoff Assigned ToChristian Grothoff  
PrioritynormalSeverityminorReproducibilityN/A
Status closedResolutionfixed 
Platformi7OSDebian GNU/LinuxOS Versionsqueeze
Product Versiongit (master) 
Target Version0.0Fixed in Version0.0 
Summary0003639: REST API sometimes sends signatures as json objects, sometimes just plain
DescriptionWe seem to have signatures sometimes together with their purpose and purpose-size in a JSON object, and sometimes just plain as the (crockford-encoded) binary blob.

As a result, the logic in the code is sometimes inconsistent, doing it one way or the other. Also, it would seem that transmitting purpose and size is, strictly speaking, redundant as we know from the context what those are.

We should for sure make sure we only use one approach for sending/receiving signatures, and maybe use one that is the least redundant?
TagsNo tags attached.

Activities

Christian Grothoff

2015-03-24 14:09

manager   ~0009045

Checked the code, all responses generated right now in taler-mint-httpd_responses.c are consistent in this.

Issue History

Date Modified Username Field Change
2015-01-29 21:03 Christian Grothoff New Issue
2015-01-29 21:12 Christian Grothoff Status new => confirmed
2015-03-22 14:28 Christian Grothoff Assigned To => Christian Grothoff
2015-03-22 14:28 Christian Grothoff Status confirmed => assigned
2015-03-24 14:09 Christian Grothoff Note Added: 0009045
2015-03-24 14:09 Christian Grothoff Status assigned => resolved
2015-03-24 14:09 Christian Grothoff Fixed in Version => 0.0
2015-03-24 14:09 Christian Grothoff Resolution open => fixed
2015-03-24 14:09 Christian Grothoff Target Version => 0.0
2015-03-24 17:57 Christian Grothoff Status resolved => closed
2016-02-18 15:43 Christian Grothoff Category mint => exchange