View Issue Details

IDProjectCategoryView StatusLast Update
0004495TalerWeb site(s)public2016-05-09 16:34
ReporterTorsten Grothoff Assigned ToFlorian Dold Resolution deadline
ImplementerReviewer 
Release signed byDeployed by 
VerifierCommunicator 
Data protection authority notification requiredNo  
CSIRT notification requiredNo  
Estimated effort (hours)Actual effort (hours)0 
Fast-trackNo
Work packagenone
PriorityimmediateSeverityblockReproducibilityhave not tried
Status closedResolutionnot fixable 
Platformi7OSDebian GNU/LinuxOS Versionsqueeze
Product Version0.0 
Target Version0.0Fixed in Version0.0 
Summary0004495: fulfillment page fails(400)
Descriptionhttps://shop.demo.taler.net/fulfillment?uuid=YGZ5DEZY8PY2HB1MSCK26RVVEWCTSEWX9TAA85XB45CTAGANECTBFK06GKE1KQV16SK6Q87HAJWNFXSE6Z1A1KMEHN2YWFZHZ6GG1W8&receiver=GNUnet&aval=10&timestamp=1462774148&tid=386032523005631&afrac=0&acurr=KUDOS
TagsNo tags attached.

Required notifications

Address or linkRemarkAdded byNotifiedActions

Relationships

related to 0004497 closedChristian Grothoff revise error responses 
related to 0004219 closedMarcello Stanisci infrastructure for headless selenium tests on taler.net missing 
has duplicate 0004494 closedFlorian Dold fulfillment page fails(502) 
related to 0004496 closedMarcello Stanisci logging is missing crucial information 

Activities

Florian Dold

2016-05-09 06:35

manager   ~0010667

Last edited: 2016-05-09 06:40

According to the logs: May 09 08:03:17-376350 taler-merchant-httpd-6244 WARNING External protocol violation detected at taler-merchant-httpd_pay.c:440.

This is clearly an instance of 0004475. The merchant does not give an appropriate error response though (a status code with a "bad request" and "hint" but no "error" is not enough ...)

I'm not sure what we can do here (except improve logging via 0004496 and error reporting via 0004497 and of course fixing 0004475).

Florian Dold

2016-05-09 06:39

manager   ~0010668

Last edited: 2016-05-09 06:40

Resolving this, since besides the related bugs I mentioned earlier there's nothing we can do directly, Torsten's wallet has "faulty" keys because the exchange screwed up at some point.

Florian Dold

2016-05-09 06:43

manager   ~0010669

Also, issues like this are why I'd like to see 0004219 resolved.

This is not something where we want to wait for users to try out our demo, the bot should do that, and open a bug or send out an email.

Christian Grothoff

2016-05-09 07:45

manager   ~0010671

We might want to improve the error message...

Florian Dold

2016-05-09 07:46

manager   ~0010672

Yeah, definitely. See related bugs ;-)

Issue History

Date ModifiedUsernameFieldChange
2016-05-09 06:13Christian GrothoffNew Issue
2016-05-09 06:13Christian GrothoffStatusnew => assigned
2016-05-09 06:13Christian GrothoffAssigned To => Florian Dold
2016-05-09 06:13Christian GrothoffReporterChristian Grothoff => Torsten Grothoff
2016-05-09 06:27Florian DoldRelationship addedrelated to 0004496
2016-05-09 06:28Florian DoldRelationship addedhas duplicate 0004494
2016-05-09 06:33Florian DoldRelationship addedrelated to 0004497
2016-05-09 06:35Florian DoldNote Added: 0010667
2016-05-09 06:39Florian DoldNote Added: 0010668
2016-05-09 06:39Florian DoldStatusassigned => informing
2016-05-09 06:39Florian DoldResolutionopen => not fixable
2016-05-09 06:40Florian DoldNote Edited: 0010668
2016-05-09 06:40Florian DoldNote Edited: 0010667
2016-05-09 06:41Florian DoldRelationship addedrelated to 0004219
2016-05-09 06:43Florian DoldNote Added: 0010669
2016-05-09 07:45Christian GrothoffNote Added: 0010671
2016-05-09 07:46Florian DoldNote Added: 0010672
2016-05-09 16:34Christian GrothoffStatusinforming => closed
2016-05-09 16:34Christian GrothoffFixed in Version => 0.0