0005219: curl-based sanity checks should check status code

ID	Project	Category	View Status	Date Submitted	Last Update

0005219	Taler	deployment and operations	public	2017-12-13 17:14	2018-04-15 20:34

Reporter	Marcello Stanisci	Assigned To	Marcello Stanisci
Priority	normal	Severity	minor	Reproducibility	have not tried
Status	closed	Resolution	fixed
Product Version	git (master)
Target Version	0.5	Fixed in Version	0.5

Summary	0005219: curl-based sanity checks should check status code
Description	Curl-based sanity checks check only whether curl returned some !=0 status code. This does not catch errors like 502-returning Web sites, because curl is still OK with those. So the HTTP status code is what should be checked.
Tags	No tags attached.

Date Modified	Username	Field	Change
2017-12-13 17:14	Marcello Stanisci	New Issue
2017-12-14 15:51	Christian Grothoff	Status	new => confirmed
2017-12-14 15:51	Christian Grothoff	Product Version	=> git (master)
2017-12-14 15:51	Christian Grothoff	Target Version	=> 0.6
2017-12-17 18:57	Marcello Stanisci	Note Added: 0012697
2017-12-18 19:54	Marcello Stanisci	Assigned To	=> Marcello Stanisci
2017-12-18 19:54	Marcello Stanisci	Status	confirmed => resolved
2017-12-18 19:54	Marcello Stanisci	Resolution	open => fixed
2017-12-18 19:54	Marcello Stanisci	Note Added: 0012698
2017-12-19 20:21	Christian Grothoff	Fixed in Version	=> 0.5
2017-12-19 20:21	Christian Grothoff	Target Version	0.6 => 0.5
2017-12-29 10:58	Marcello Stanisci	Relationship added	has duplicate 0005199
2018-04-15 20:34	Christian Grothoff	Status	resolved => closed

Marcello Stanisci 2017-12-17 18:57 reporter ~0012697	use the '-w' option, like: curl -s -o /dev/null -w "%{http_code}" https://www.example.com/

Marcello Stanisci 2017-12-18 19:54 reporter ~0012698	fixed @ b4ef813