0004830: Caching breaks payment

ID	Project	Category	View Status	Date Submitted	Last Update
0004830	Taler	other	public	2016-12-05 16:16	2017-06-06 12:18

Reporter	Marcello Stanisci	Assigned To	Marcello Stanisci	Resolution deadline
Implementer		Reviewer
Release signed by		Deployed by
Verifier		Communicator
Data protection authority notification required	No
CSIRT notification required	No
Estimated effort (hours)		Actual effort (hours)	0
Fast-track	No
Work package	none
Priority	high	Severity	minor	Reproducibility	have not tried
Status	closed	Resolution	fixed
Product Version	git (master)
Target Version	0.3	Fixed in Version	0.3

Summary	0004830: Caching breaks payment
Description	The tutorial merchant fails to finalize a payment because when it visits the fulfillment page it soon gets the page from a previous payment, resulting in NOT going through the payment protocol implemented in the fulfillment page.
Tags	No tags attached.

Date Modified	Username	Field	Change
2016-12-05 16:16	Marcello Stanisci	New Issue
2016-12-16 10:11	Marcello Stanisci	Assigned To	=> Marcello Stanisci
2016-12-16 10:11	Marcello Stanisci	Status	new => assigned
2016-12-16 10:11	Marcello Stanisci	Priority	normal => high
2016-12-16 14:19	Marcello Stanisci	Status	assigned => informing
2016-12-16 14:19	Marcello Stanisci	Resolution	open => fixed
2016-12-16 14:19	Marcello Stanisci	Note Added: 0011593
2017-01-16 09:21	Christian Grothoff	Product Version	=> git (master)
2017-01-16 09:21	Christian Grothoff	Fixed in Version	=> 0.3
2017-01-16 09:21	Christian Grothoff	Target Version	=> 0.3
2017-06-06 12:18	Christian Grothoff	Status	informing => closed

Marcello Stanisci 2016-12-16 14:19 reporter ~0011593	Not a caching issue at all! Payments subsequent to a successful one would find the "payed" state still active so would just show the fulfillment page from the previous payment. Explicitly destroying the session fixed it (725e428).