Martin Højriis Kristensens hjemmeside

Link Status

Linkhttp://gis.aarhus.dk/lokalplaner/pdf/aarhus/pdf/lokplan.150/694!.pdf
Oprettet2008-01-07 01:00:00
StatusAntageligvis OK
Lokal Cache (bedst for bilag)Ikke tilgængelig for aktive links
Archive.org Cache (bedst for sider)https://web.archive.org/web/20080107/http://gis.aarhus.dk/lokalplaner/pdf/aarhus/pdf/lokplan.150/694!.pdf
Seneste HTTP-svar HTTP/1.1 200 OK
Typisk HTTP-svar seneste uge
Link Historik
Dato http_response content_type content_length Titel
04/10-15 HTTP/1.1 200 OK application/pdf 1763643
04/10-15 HTTP/1.1 200 OK application/pdf 1763643
05/10-15 HTTP/1.1 200 OK application/pdf 1763643
05/10-15 HTTP/1.1 200 OK application/pdf 1763643
06/10-15 HTTP/1.1 200 OK application/pdf 1763643
07/10-15 HTTP/1.1 200 OK application/pdf 1763643
08/10-15 HTTP/1.1 200 OK application/pdf 1763643
08/10-15 HTTP/1.1 200 OK application/pdf 1763643
09/10-15 HTTP/1.1 200 OK application/pdf 1763643
10/10-15 HTTP/1.1 200 OK application/pdf 1763643
11/10-15 HTTP/1.1 200 OK application/pdf 1763643
11/10-15 HTTP/1.1 200 OK application/pdf 1763643
12/10-15 HTTP/1.1 200 OK application/pdf 1763643
12/10-15 HTTP/1.1 200 OK application/pdf 1763643
14/10-15 HTTP/1.1 200 OK application/pdf 1763643
14/10-15 HTTP/1.1 200 OK application/pdf 1763643
15/10-15 HTTP/1.1 200 OK application/pdf 1763643
15/10-15 HTTP/1.1 200 OK application/pdf 1763643
17/10-15 HTTP/1.1 200 OK application/pdf 1763643
17/10-15 HTTP/1.1 200 OK application/pdf 1763643
18/10-15 HTTP/1.1 200 OK application/pdf 1763643
18/10-15 HTTP/1.1 200 OK application/pdf 1763643
20/10-15 HTTP/1.1 200 OK application/pdf 1763643
20/10-15 HTTP/1.1 200 OK application/pdf 1763643
22/10-15 HTTP/1.1 200 OK application/pdf 1763643
22/10-15 HTTP/1.1 200 OK application/pdf 1763643
24/10-15 HTTP/1.1 200 OK application/pdf 1763643
24/10-15 HTTP/1.1 200 OK application/pdf 1763643
26/10-15 HTTP/1.1 200 OK application/pdf 1763643
26/10-15 HTTP/1.1 200 OK application/pdf 1763643
27/10-15 HTTP/1.1 200 OK application/pdf 1763643
27/10-15 HTTP/1.1 200 OK application/pdf 1763643
29/10-15 HTTP/1.1 200 OK application/pdf 1763643
29/10-15 HTTP/1.1 200 OK application/pdf 1763643
31/10-15 HTTP/1.1 200 OK application/pdf 1763643
31/10-15 HTTP/1.1 200 OK application/pdf 1763643
02/11-15 HTTP/1.1 200 OK application/pdf 1763643
02/11-15 HTTP/1.1 200 OK application/pdf 1763643
04/11-15 HTTP/1.1 200 OK application/pdf 1763643
04/11-15 HTTP/1.1 200 OK application/pdf 1763643
06/11-15 HTTP/1.1 200 OK application/pdf 1763643
06/11-15 HTTP/1.1 200 OK application/pdf 1763643
08/11-15 HTTP/1.1 200 OK application/pdf 1763643
08/11-15 HTTP/1.1 200 OK application/pdf 1763643
10/11-15 HTTP/1.1 200 OK application/pdf 1763643
10/11-15 HTTP/1.1 200 OK application/pdf 1763643
12/11-15 HTTP/1.1 200 OK application/pdf 1763643
12/11-15 HTTP/1.1 200 OK application/pdf 1763643
14/11-15 HTTP/1.1 200 OK application/pdf 1763643
14/11-15 HTTP/1.1 200 OK application/pdf 1763643
16/11-15 HTTP/1.1 200 OK application/pdf 1763643
16/11-15 HTTP/1.1 200 OK application/pdf 1763643
18/11-15 HTTP/1.1 200 OK application/pdf 1763643
18/11-15 HTTP/1.1 200 OK application/pdf 1763643
20/11-15 HTTP/1.1 200 OK application/pdf 1763643
20/11-15 HTTP/1.1 200 OK application/pdf 1763643
22/11-15 HTTP/1.1 200 OK application/pdf 1763643
22/11-15 HTTP/1.1 200 OK application/pdf 1763643
24/11-15 HTTP/1.1 200 OK application/pdf 1763643
24/11-15 HTTP/1.1 200 OK application/pdf 1763643
26/11-15 HTTP/1.1 200 OK application/pdf 1763643
26/11-15 HTTP/1.1 200 OK application/pdf 1763643
28/11-15 HTTP/1.1 200 OK application/pdf 1763643
28/11-15 HTTP/1.1 200 OK application/pdf 1763643
30/11-15 HTTP/1.1 200 OK application/pdf 1763643
30/11-15 HTTP/1.1 200 OK application/pdf 1763643
02/12-15 HTTP/1.1 200 OK application/pdf 1763643
02/12-15 HTTP/1.1 200 OK application/pdf 1763643
04/12-15 HTTP/1.1 200 OK application/pdf 1763643
04/12-15 HTTP/1.1 200 OK application/pdf 1763643
06/12-15 HTTP/1.1 200 OK application/pdf 1763643
06/12-15 HTTP/1.1 200 OK application/pdf 1763643
08/12-15 HTTP/1.1 200 OK application/pdf 1763643
08/12-15 HTTP/1.1 200 OK application/pdf 1763643
10/12-15 HTTP/1.1 200 OK application/pdf 1763643
10/12-15 HTTP/1.1 200 OK application/pdf 1763643
12/12-15 HTTP/1.1 200 OK application/pdf 1763643
12/12-15 HTTP/1.1 200 OK application/pdf 1763643
14/12-15 HTTP/1.1 200 OK application/pdf 1763643
14/12-15 HTTP/1.1 200 OK application/pdf 1763643
16/12-15 HTTP/1.1 200 OK application/pdf 1763643
16/12-15 HTTP/1.1 200 OK application/pdf 1763643
18/12-15 HTTP/1.1 200 OK application/pdf 1763643
18/12-15 HTTP/1.1 200 OK application/pdf 1763643
20/12-15 HTTP/1.1 200 OK application/pdf 1763643
20/12-15 HTTP/1.1 200 OK application/pdf 1763643
22/12-15 HTTP/1.1 200 OK application/pdf 1763643
22/12-15 HTTP/1.1 200 OK application/pdf 1763643
24/12-15 HTTP/1.1 200 OK application/pdf 1763643
24/12-15 HTTP/1.1 200 OK application/pdf 1763643
26/12-15 HTTP/1.1 200 OK application/pdf 1763643
26/12-15 HTTP/1.1 200 OK application/pdf 1763643
28/12-15 HTTP/1.1 200 OK application/pdf 1763643
28/12-15 HTTP/1.1 200 OK application/pdf 1763643
30/12-15 HTTP/1.1 200 OK application/pdf 1763643
30/12-15 HTTP/1.1 200 OK application/pdf 1763643
31/12-15 HTTP/1.1 200 OK application/pdf 1763643
31/12-15 HTTP/1.1 200 OK application/pdf 1763643
02/01-16 HTTP/1.1 200 OK application/pdf 1763643
02/01-16 HTTP/1.1 200 OK application/pdf 1763643
04/01-16 HTTP/1.1 200 OK application/pdf 1763643
04/01-16 HTTP/1.1 200 OK application/pdf 1763643
06/01-16 HTTP/1.1 200 OK application/pdf 1763643
06/01-16 HTTP/1.1 200 OK application/pdf 1763643
08/01-16 HTTP/1.1 200 OK application/pdf 1763643
08/01-16 HTTP/1.1 200 OK application/pdf 1763643
10/01-16 HTTP/1.1 200 OK application/pdf 1763643
10/01-16 HTTP/1.1 200 OK application/pdf 1763643
12/01-16 HTTP/1.1 200 OK application/pdf 1763643
12/01-16 HTTP/1.1 200 OK application/pdf 1763643
14/01-16 HTTP/1.1 200 OK application/pdf 1763643
14/01-16 HTTP/1.1 200 OK application/pdf 1763643
15/01-16 HTTP/1.1 200 OK application/pdf 1763643
15/01-16 HTTP/1.1 200 OK application/pdf 1763643
17/01-16 HTTP/1.1 200 OK application/pdf 1763643
17/01-16 HTTP/1.1 200 OK application/pdf 1763643
19/01-16 HTTP/1.1 200 OK application/pdf 1763643
19/01-16 HTTP/1.1 200 OK application/pdf 1763643
21/01-16 HTTP/1.1 200 OK application/pdf 1763643
21/01-16 HTTP/1.1 200 OK application/pdf 1763643
23/01-16 HTTP/1.1 200 OK application/pdf 1763643
23/01-16 HTTP/1.1 200 OK application/pdf 1763643
25/01-16 HTTP/1.1 200 OK application/pdf 1763643
25/01-16 HTTP/1.1 200 OK application/pdf 1763643
27/01-16 HTTP/1.1 200 OK application/pdf 1763643
28/01-16 HTTP/1.1 200 OK application/pdf 1763643
29/01-16 HTTP/1.1 200 OK application/pdf 1763643
29/01-16 HTTP/1.1 200 OK application/pdf 1763643
30/01-16 HTTP/1.1 200 OK application/pdf 1763643
31/01-16 HTTP/1.1 200 OK application/pdf 1763643
01/02-16 HTTP/1.1 200 OK application/pdf 1763643
01/02-16 HTTP/1.1 200 OK application/pdf 1763643
02/02-16 HTTP/1.1 200 OK application/pdf 1763643
03/02-16 HTTP/1.1 200 OK application/pdf 1763643
04/02-16 HTTP/1.1 200 OK application/pdf 1763643
04/02-16 HTTP/1.1 200 OK application/pdf 1763643
05/02-16 HTTP/1.1 200 OK application/pdf 1763643
05/02-16 HTTP/1.1 200 OK application/pdf 1763643
07/02-16 HTTP/1.1 200 OK application/pdf 1763643
07/02-16 HTTP/1.1 200 OK application/pdf 1763643
08/02-16 HTTP/1.1 200 OK application/pdf 1763643
08/02-16 HTTP/1.1 200 OK application/pdf 1763643
10/02-16 HTTP/1.1 200 OK application/pdf 1763643
10/02-16 HTTP/1.1 200 OK application/pdf 1763643
11/02-16 HTTP/1.1 200 OK application/pdf 1763643
11/02-16 HTTP/1.1 200 OK application/pdf 1763643
13/02-16 HTTP/1.1 200 OK application/pdf 1763643
13/02-16 HTTP/1.1 200 OK application/pdf 1763643
14/02-16 N/A 0
14/02-16 N/A 0
16/02-16 HTTP/1.1 200 OK application/pdf 1763643
16/02-16 HTTP/1.1 200 OK application/pdf 1763643
17/02-16 HTTP/1.1 200 OK application/pdf 1763643
17/02-16 HTTP/1.1 200 OK application/pdf 1763643
19/02-16 HTTP/1.1 200 OK application/pdf 1763643
19/02-16 HTTP/1.1 200 OK application/pdf 1763643
20/02-16 HTTP/1.1 200 OK application/pdf 1763643
20/02-16 HTTP/1.1 200 OK application/pdf 1763643
21/02-16 HTTP/1.1 200 OK application/pdf 1763643
22/02-16 HTTP/1.1 200 OK application/pdf 1763643
23/02-16 HTTP/1.1 200 OK application/pdf 1763643
23/02-16 HTTP/1.1 200 OK application/pdf 1763643
24/02-16 HTTP/1.1 200 OK application/pdf 1763643
25/02-16 HTTP/1.1 200 OK application/pdf 1763643
26/02-16 HTTP/1.1 200 OK application/pdf 1763643
26/02-16 HTTP/1.1 200 OK application/pdf 1763643
27/02-16 HTTP/1.1 200 OK application/pdf 1763643
27/02-16 HTTP/1.1 200 OK application/pdf 1763643
29/02-16 HTTP/1.1 200 OK application/pdf 1763643
29/02-16 HTTP/1.1 200 OK application/pdf 1763643
01/03-16 HTTP/1.1 200 OK application/pdf 1763643
01/03-16 HTTP/1.1 200 OK application/pdf 1763643
03/03-16 HTTP/1.1 200 OK application/pdf 1763643
03/03-16 HTTP/1.1 200 OK application/pdf 1763643
04/03-16 HTTP/1.1 200 OK application/pdf 1763643
04/03-16 HTTP/1.1 200 OK application/pdf 1763643
06/03-16 HTTP/1.1 200 OK application/pdf 1763643
06/03-16 HTTP/1.1 200 OK application/pdf 1763643
07/03-16 HTTP/1.1 200 OK application/pdf 1763643
07/03-16 HTTP/1.1 200 OK application/pdf 1763643
09/03-16 HTTP/1.1 200 OK application/pdf 1763643
09/03-16 HTTP/1.1 200 OK application/pdf 1763643
10/03-16 HTTP/1.1 200 OK application/pdf 1763643
10/03-16 HTTP/1.1 200 OK application/pdf 1763643
12/03-16 HTTP/1.1 200 OK application/pdf 1763643
12/03-16 HTTP/1.1 200 OK application/pdf 1763643
13/03-16 HTTP/1.1 200 OK application/pdf 1763643
13/03-16 HTTP/1.1 200 OK application/pdf 1763643
14/03-16 HTTP/1.1 200 OK application/pdf 1763643
15/03-16 HTTP/1.1 200 OK application/pdf 1763643
16/03-16 HTTP/1.1 200 OK application/pdf 1763643
16/03-16 HTTP/1.1 200 OK application/pdf 1763643
17/03-16 HTTP/1.1 200 OK application/pdf 1763643
18/03-16 HTTP/1.1 200 OK application/pdf 1763643
19/03-16 HTTP/1.1 200 OK application/pdf 1763643
19/03-16 HTTP/1.1 200 OK application/pdf 1763643
20/03-16 HTTP/1.1 200 OK application/pdf 1763643
21/03-16 HTTP/1.1 200 OK application/pdf 1763643
22/03-16 HTTP/1.1 200 OK application/pdf 1763643
22/03-16 HTTP/1.1 200 OK application/pdf 1763643
23/03-16 HTTP/1.1 200 OK application/pdf 1763643
24/03-16 HTTP/1.1 200 OK application/pdf 1763643
25/03-16 HTTP/1.1 200 OK application/pdf 1763643
25/03-16 HTTP/1.1 200 OK application/pdf 1763643
26/03-16 HTTP/1.1 200 OK application/pdf 1763643
27/03-16 HTTP/1.1 200 OK application/pdf 1763643
28/03-16 HTTP/1.1 200 OK application/pdf 1763643
28/03-16 HTTP/1.1 200 OK application/pdf 1763643
29/03-16 HTTP/1.1 200 OK application/pdf 1763643
30/03-16 HTTP/1.1 200 OK application/pdf 1763643
31/03-16 HTTP/1.1 200 OK application/pdf 1763643
31/03-16 HTTP/1.1 200 OK application/pdf 1763643
01/04-16 HTTP/1.1 200 OK application/pdf 1763643
02/04-16 HTTP/1.1 200 OK application/pdf 1763643
03/04-16 HTTP/1.1 200 OK application/pdf 1763643
03/04-16 HTTP/1.1 200 OK application/pdf 1763643
04/04-16 HTTP/1.1 200 OK application/pdf 1763643
05/04-16 HTTP/1.1 200 OK application/pdf 1763643
06/04-16 HTTP/1.1 200 OK application/pdf 1763643
06/04-16 HTTP/1.1 200 OK application/pdf 1763643
07/04-16 HTTP/1.1 200 OK application/pdf 1763643
08/04-16 HTTP/1.1 200 OK application/pdf 1763643
09/04-16 HTTP/1.1 200 OK application/pdf 1763643
09/04-16 HTTP/1.1 200 OK application/pdf 1763643
10/04-16 HTTP/1.1 200 OK application/pdf 1763643
11/04-16 HTTP/1.1 200 OK application/pdf 1763643
12/04-16 HTTP/1.1 200 OK application/pdf 1763643
12/04-16 HTTP/1.1 200 OK application/pdf 1763643
13/04-16 HTTP/1.1 200 OK application/pdf 1763643
14/04-16 HTTP/1.1 200 OK application/pdf 1763643
15/04-16 HTTP/1.1 200 OK application/pdf 1763643
16/04-16 HTTP/1.1 200 OK application/pdf 1763643
17/04-16 HTTP/1.1 200 OK application/pdf 1763643
17/04-16 HTTP/1.1 200 OK application/pdf 1763643
18/04-16 HTTP/1.1 200 OK application/pdf 1763643
19/04-16 HTTP/1.1 200 OK application/pdf 1763643
19/04-16 HTTP/1.1 200 OK application/pdf 1763643
19/04-16 HTTP/1.1 200 OK application/pdf 1763643
19/04-16 HTTP/1.1 200 OK application/pdf 1763643
20/04-16 N/A 0
20/04-16 HTTP/1.1 200 OK application/pdf 1763643
20/04-16 HTTP/1.1 200 OK application/pdf 1763643
20/04-16 HTTP/1.1 200 OK application/pdf 1763643
20/04-16 HTTP/1.1 200 OK application/pdf 1763643
21/04-16 HTTP/1.1 200 OK application/pdf 1763643
21/04-16 HTTP/1.1 200 OK application/pdf 1763643
21/04-16 HTTP/1.1 200 OK application/pdf 1763643
21/04-16 HTTP/1.1 200 OK application/pdf 1763643
21/04-16 HTTP/1.1 200 OK application/pdf 1763643
21/04-16 HTTP/1.1 200 OK application/pdf 1763643
22/04-16 HTTP/1.1 200 OK application/pdf 1763643
22/04-16 HTTP/1.1 200 OK application/pdf 1763643
22/04-16 HTTP/1.1 200 OK application/pdf 1763643
22/04-16 HTTP/1.1 200 OK application/pdf 1763643
22/04-16 HTTP/1.1 200 OK application/pdf 1763643
23/04-16 HTTP/1.1 200 OK application/pdf 1763643
23/04-16 HTTP/1.1 200 OK application/pdf 1763643
23/04-16 HTTP/1.1 200 OK application/pdf 1763643
23/04-16 HTTP/1.1 200 OK application/pdf 1763643
23/04-16 HTTP/1.1 200 OK application/pdf 1763643
24/04-16 HTTP/1.1 200 OK application/pdf 1763643
24/04-16 HTTP/1.1 200 OK application/pdf 1763643
24/04-16 HTTP/1.1 200 OK application/pdf 1763643
24/04-16 HTTP/1.1 200 OK application/pdf 1763643
24/04-16 HTTP/1.1 200 OK application/pdf 1763643
24/04-16 HTTP/1.1 200 OK application/pdf 1763643
25/04-16 HTTP/1.1 200 OK application/pdf 1763643
25/04-16 HTTP/1.1 200 OK application/pdf 1763643
25/04-16 HTTP/1.1 200 OK application/pdf 1763643
25/04-16 HTTP/1.1 200 OK application/pdf 1763643
25/04-16 HTTP/1.1 200 OK application/pdf 1763643
25/04-16 HTTP/1.1 200 OK application/pdf 1763643
26/04-16 HTTP/1.1 200 OK application/pdf 1763643
26/04-16 HTTP/1.1 200 OK application/pdf 1763643
26/04-16 HTTP/1.1 200 OK application/pdf 1763643
26/04-16 HTTP/1.1 200 OK application/pdf 1763643
26/04-16 HTTP/1.1 200 OK application/pdf 1763643
27/04-16 HTTP/1.1 200 OK application/pdf 1763643
27/04-16 HTTP/1.1 200 OK application/pdf 1763643
27/04-16 HTTP/1.1 200 OK application/pdf 1763643
27/04-16 HTTP/1.1 200 OK application/pdf 1763643
27/04-16 HTTP/1.1 200 OK application/pdf 1763643
27/04-16 HTTP/1.1 200 OK application/pdf 1763643
28/04-16 HTTP/1.1 200 OK application/pdf 1763643
28/04-16 HTTP/1.1 200 OK application/pdf 1763643
28/04-16 HTTP/1.1 200 OK application/pdf 1763643
28/04-16 HTTP/1.1 200 OK application/pdf 1763643
28/04-16 HTTP/1.1 200 OK application/pdf 1763643
29/04-16 HTTP/1.1 200 OK application/pdf 1763643
29/04-16 HTTP/1.1 200 OK application/pdf 1763643
29/04-16 HTTP/1.1 200 OK application/pdf 1763643
29/04-16 HTTP/1.1 200 OK application/pdf 1763643
29/04-16 HTTP/1.1 200 OK application/pdf 1763643
29/04-16 HTTP/1.1 200 OK application/pdf 1763643
30/04-16 HTTP/1.1 200 OK application/pdf 1763643
30/04-16 HTTP/1.1 200 OK application/pdf 1763643
30/04-16 HTTP/1.1 200 OK application/pdf 1763643
30/04-16 HTTP/1.1 200 OK application/pdf 1763643
30/04-16 HTTP/1.1 200 OK application/pdf 1763643
01/05-16 HTTP/1.1 200 OK application/pdf 1763643
01/05-16 HTTP/1.1 200 OK application/pdf 1763643
01/05-16 HTTP/1.1 200 OK application/pdf 1763643
01/05-16 HTTP/1.1 200 OK application/pdf 1763643
01/05-16 HTTP/1.1 200 OK application/pdf 1763643
02/05-16 HTTP/1.1 200 OK application/pdf 1763643
02/05-16 HTTP/1.1 200 OK application/pdf 1763643
02/05-16 HTTP/1.1 200 OK application/pdf 1763643
02/05-16 HTTP/1.1 200 OK application/pdf 1763643
02/05-16 HTTP/1.1 200 OK application/pdf 1763643
02/05-16 HTTP/1.1 200 OK application/pdf 1763643
03/05-16 HTTP/1.1 200 OK application/pdf 1763643
03/05-16 HTTP/1.1 200 OK application/pdf 1763643
03/05-16 HTTP/1.1 200 OK application/pdf 1763643
03/05-16 HTTP/1.1 200 OK application/pdf 1763643
03/05-16 HTTP/1.1 200 OK application/pdf 1763643
04/05-16 HTTP/1.1 200 OK application/pdf 1763643
04/05-16 HTTP/1.1 200 OK application/pdf 1763643
04/05-16 HTTP/1.1 200 OK application/pdf 1763643
04/05-16 HTTP/1.1 200 OK application/pdf 1763643
04/05-16 HTTP/1.1 200 OK application/pdf 1763643
04/05-16 HTTP/1.1 200 OK application/pdf 1763643
05/05-16 HTTP/1.1 200 OK application/pdf 1763643
05/05-16 HTTP/1.1 200 OK application/pdf 1763643
05/05-16 HTTP/1.1 200 OK application/pdf 1763643
05/05-16 HTTP/1.1 200 OK application/pdf 1763643
05/05-16 HTTP/1.1 200 OK application/pdf 1763643
06/05-16 HTTP/1.1 200 OK application/pdf 1763643
06/05-16 HTTP/1.1 200 OK application/pdf 1763643
06/05-16 HTTP/1.1 200 OK application/pdf 1763643
06/05-16 HTTP/1.1 200 OK application/pdf 1763643
06/05-16 HTTP/1.1 200 OK application/pdf 1763643
07/05-16 HTTP/1.1 200 OK application/pdf 1763643
07/05-16 HTTP/1.1 200 OK application/pdf 1763643
07/05-16 HTTP/1.1 200 OK application/pdf 1763643
07/05-16 HTTP/1.1 200 OK application/pdf 1763643
07/05-16 HTTP/1.1 200 OK application/pdf 1763643
07/05-16 HTTP/1.1 200 OK application/pdf 1763643
08/05-16 HTTP/1.1 200 OK application/pdf 1763643
08/05-16 HTTP/1.1 200 OK application/pdf 1763643
08/05-16 HTTP/1.1 200 OK application/pdf 1763643
08/05-16 HTTP/1.1 200 OK application/pdf 1763643
08/05-16 HTTP/1.1 200 OK application/pdf 1763643
09/05-16 HTTP/1.1 200 OK application/pdf 1763643
09/05-16 HTTP/1.1 200 OK application/pdf 1763643
09/05-16 HTTP/1.1 200 OK application/pdf 1763643
09/05-16 HTTP/1.1 200 OK application/pdf 1763643
09/05-16 HTTP/1.1 200 OK application/pdf 1763643
10/05-16 HTTP/1.1 200 OK application/pdf 1763643
10/05-16 HTTP/1.1 200 OK application/pdf 1763643
10/05-16 HTTP/1.1 200 OK application/pdf 1763643
10/05-16 HTTP/1.1 200 OK application/pdf 1763643
10/05-16 HTTP/1.1 200 OK application/pdf 1763643
10/05-16 HTTP/1.1 200 OK application/pdf 1763643
11/05-16 HTTP/1.1 200 OK application/pdf 1763643
11/05-16 HTTP/1.1 200 OK application/pdf 1763643
11/05-16 HTTP/1.1 200 OK application/pdf 1763643
11/05-16 HTTP/1.1 200 OK application/pdf 1763643
11/05-16 HTTP/1.1 200 OK application/pdf 1763643
12/05-16 HTTP/1.1 200 OK application/pdf 1763643
12/05-16 HTTP/1.1 200 OK application/pdf 1763643
12/05-16 HTTP/1.1 200 OK application/pdf 1763643
12/05-16 HTTP/1.1 200 OK application/pdf 1763643
12/05-16 HTTP/1.1 200 OK application/pdf 1763643
12/05-16 HTTP/1.1 200 OK application/pdf 1763643
13/05-16 HTTP/1.1 200 OK application/pdf 1763643
13/05-16 HTTP/1.1 200 OK application/pdf 1763643
13/05-16 HTTP/1.1 200 OK application/pdf 1763643
13/05-16 HTTP/1.1 200 OK application/pdf 1763643
13/05-16 HTTP/1.1 200 OK application/pdf 1763643
14/05-16 HTTP/1.1 200 OK application/pdf 1763643
14/05-16 HTTP/1.1 200 OK application/pdf 1763643
14/05-16 HTTP/1.1 200 OK application/pdf 1763643
14/05-16 HTTP/1.1 200 OK application/pdf 1763643
14/05-16 HTTP/1.1 200 OK application/pdf 1763643
14/05-16 HTTP/1.1 200 OK application/pdf 1763643
15/05-16 HTTP/1.1 200 OK application/pdf 1763643
15/05-16 HTTP/1.1 200 OK application/pdf 1763643
15/05-16 HTTP/1.1 200 OK application/pdf 1763643
15/05-16 HTTP/1.1 200 OK application/pdf 1763643
15/05-16 HTTP/1.1 200 OK application/pdf 1763643
16/05-16 HTTP/1.1 200 OK application/pdf 1763643
16/05-16 HTTP/1.1 200 OK application/pdf 1763643
16/05-16 HTTP/1.1 200 OK application/pdf 1763643
16/05-16 HTTP/1.1 200 OK application/pdf 1763643
16/05-16 HTTP/1.1 200 OK application/pdf 1763643
17/05-16 HTTP/1.1 200 OK application/pdf 1763643
17/05-16 HTTP/1.1 200 OK application/pdf 1763643
17/05-16 HTTP/1.1 200 OK application/pdf 1763643
17/05-16 HTTP/1.1 200 OK application/pdf 1763643
17/05-16 HTTP/1.1 200 OK application/pdf 1763643
17/05-16 HTTP/1.1 200 OK application/pdf 1763643
18/05-16 HTTP/1.1 200 OK application/pdf 1763643
18/05-16 HTTP/1.1 200 OK application/pdf 1763643
18/05-16 HTTP/1.1 200 OK application/pdf 1763643
18/05-16 HTTP/1.1 200 OK application/pdf 1763643
18/05-16 HTTP/1.1 200 OK application/pdf 1763643
19/05-16 HTTP/1.1 200 OK application/pdf 1763643
19/05-16 HTTP/1.1 200 OK application/pdf 1763643
19/05-16 HTTP/1.1 200 OK application/pdf 1763643
19/05-16 HTTP/1.1 200 OK application/pdf 1763643
19/05-16 HTTP/1.1 200 OK application/pdf 1763643
19/05-16 HTTP/1.1 200 OK application/pdf 1763643
20/05-16 HTTP/1.1 200 OK application/pdf 1763643
20/05-16 HTTP/1.1 200 OK application/pdf 1763643
20/05-16 HTTP/1.1 200 OK application/pdf 1763643
20/05-16 HTTP/1.1 200 OK application/pdf 1763643
20/05-16 HTTP/1.1 200 OK application/pdf 1763643
21/05-16 HTTP/1.1 200 OK application/pdf 1763643
21/05-16 HTTP/1.1 200 OK application/pdf 1763643
21/05-16 HTTP/1.1 200 OK application/pdf 1763643
21/05-16 HTTP/1.1 200 OK application/pdf 1763643
21/05-16 HTTP/1.1 200 OK application/pdf 1763643
22/05-16 HTTP/1.1 200 OK application/pdf 1763643
22/05-16 HTTP/1.1 200 OK application/pdf 1763643
22/05-16 HTTP/1.1 200 OK application/pdf 1763643
22/05-16 HTTP/1.1 200 OK application/pdf 1763643
22/05-16 HTTP/1.1 200 OK application/pdf 1763643
22/05-16 HTTP/1.1 200 OK application/pdf 1763643
23/05-16 HTTP/1.1 200 OK application/pdf 1763643
23/05-16 HTTP/1.1 200 OK application/pdf 1763643
23/05-16 HTTP/1.1 200 OK application/pdf 1763643
23/05-16 HTTP/1.1 200 OK application/pdf 1763643
23/05-16 HTTP/1.1 200 OK application/pdf 1763643
24/05-16 HTTP/1.1 200 OK application/pdf 1763643
24/05-16 HTTP/1.1 200 OK application/pdf 1763643
24/05-16 HTTP/1.1 200 OK application/pdf 1763643
24/05-16 HTTP/1.1 200 OK application/pdf 1763643
24/05-16 HTTP/1.1 200 OK application/pdf 1763643
25/05-16 HTTP/1.1 200 OK application/pdf 1763643
25/05-16 HTTP/1.1 200 OK application/pdf 1763643
25/05-16 HTTP/1.1 200 OK application/pdf 1763643
25/05-16 HTTP/1.1 200 OK application/pdf 1763643
25/05-16 HTTP/1.1 200 OK application/pdf 1763643
25/05-16 HTTP/1.1 200 OK application/pdf 1763643
26/05-16 HTTP/1.1 200 OK application/pdf 1763643
26/05-16 HTTP/1.1 200 OK application/pdf 1763643
26/05-16 HTTP/1.1 200 OK application/pdf 1763643
26/05-16 HTTP/1.1 200 OK application/pdf 1763643
26/05-16 HTTP/1.1 200 OK application/pdf 1763643
27/05-16 HTTP/1.1 200 OK application/pdf 1763643
27/05-16 HTTP/1.1 200 OK application/pdf 1763643
27/05-16 HTTP/1.1 200 OK application/pdf 1763643
27/05-16 HTTP/1.1 200 OK application/pdf 1838195
27/05-16 HTTP/1.1 200 OK application/pdf 1838195
27/05-16 HTTP/1.1 200 OK application/pdf 1838195
28/05-16 HTTP/1.1 200 OK application/pdf 1838195
28/05-16 HTTP/1.1 200 OK application/pdf 1838195
28/05-16 HTTP/1.1 200 OK application/pdf 1838195
28/05-16 HTTP/1.1 200 OK application/pdf 1838195
28/05-16 HTTP/1.1 200 OK application/pdf 1838195
29/05-16 N/A 0
29/05-16 HTTP/1.1 200 OK application/pdf 1838195
29/05-16 HTTP/1.1 200 OK application/pdf 1838195
29/05-16 HTTP/1.1 200 OK application/pdf 1838195
29/05-16 HTTP/1.1 200 OK application/pdf 1838195
29/05-16 HTTP/1.1 200 OK application/pdf 1838195
30/05-16 HTTP/1.1 200 OK application/pdf 1838195
30/05-16 HTTP/1.1 200 OK application/pdf 1838195
30/05-16 HTTP/1.1 200 OK application/pdf 1838195
30/05-16 HTTP/1.1 200 OK application/pdf 1838195
30/05-16 HTTP/1.1 200 OK application/pdf 1838195
31/05-16 HTTP/1.1 200 OK application/pdf 1838195
31/05-16 HTTP/1.1 200 OK application/pdf 1838195
31/05-16 HTTP/1.1 200 OK application/pdf 1838195
31/05-16 HTTP/1.1 200 OK application/pdf 1838195
31/05-16 HTTP/1.1 200 OK application/pdf 1838195
01/06-16 HTTP/1.1 200 OK application/pdf 1838195
01/06-16 HTTP/1.1 200 OK application/pdf 1838195
01/06-16 HTTP/1.1 200 OK application/pdf 1838195
01/06-16 HTTP/1.1 200 OK application/pdf 1838195
01/06-16 HTTP/1.1 200 OK application/pdf 1838195
02/06-16 HTTP/1.1 200 OK application/pdf 1838195
02/06-16 HTTP/1.1 200 OK application/pdf 1838195
02/06-16 HTTP/1.1 200 OK application/pdf 1838195
02/06-16 HTTP/1.1 200 OK application/pdf 1838195
02/06-16 HTTP/1.1 200 OK application/pdf 1838195
02/06-16 HTTP/1.1 200 OK application/pdf 1838195
03/06-16 HTTP/1.1 200 OK application/pdf 1838195
03/06-16 HTTP/1.1 200 OK application/pdf 1838195
03/06-16 HTTP/1.1 200 OK application/pdf 1838195
03/06-16 HTTP/1.1 200 OK application/pdf 1838195
03/06-16 HTTP/1.1 200 OK application/pdf 1838195
04/06-16 HTTP/1.1 200 OK application/pdf 1838195
04/06-16 HTTP/1.1 200 OK application/pdf 1838195
04/06-16 HTTP/1.1 200 OK application/pdf 1838195
04/06-16 HTTP/1.1 200 OK application/pdf 1838195
04/06-16 HTTP/1.1 200 OK application/pdf 1838195
05/06-16 HTTP/1.1 200 OK application/pdf 1838195
05/06-16 HTTP/1.1 200 OK application/pdf 1838195
05/06-16 HTTP/1.1 200 OK application/pdf 1838195
05/06-16 HTTP/1.1 200 OK application/pdf 1838195
05/06-16 HTTP/1.1 200 OK application/pdf 1838195
05/06-16 HTTP/1.1 200 OK application/pdf 1838195
06/06-16 HTTP/1.1 200 OK application/pdf 1838195
06/06-16 HTTP/1.1 200 OK application/pdf 1838195
06/06-16 HTTP/1.1 200 OK application/pdf 1838195
06/06-16 HTTP/1.1 200 OK application/pdf 1838195
06/06-16 HTTP/1.1 200 OK application/pdf 1838195
07/06-16 HTTP/1.1 200 OK application/pdf 1838195
07/06-16 HTTP/1.1 200 OK application/pdf 1838195
07/06-16 HTTP/1.1 200 OK application/pdf 1838195
07/06-16 HTTP/1.1 200 OK application/pdf 1838195
07/06-16 HTTP/1.1 200 OK application/pdf 1838195
07/06-16 HTTP/1.1 200 OK application/pdf 1838195
08/06-16 HTTP/1.1 200 OK application/pdf 1838195
08/06-16 HTTP/1.1 200 OK application/pdf 1838195
08/06-16 HTTP/1.1 200 OK application/pdf 1838195
08/06-16 HTTP/1.1 200 OK application/pdf 1838195
08/06-16 HTTP/1.1 200 OK application/pdf 1838195
09/06-16 HTTP/1.1 200 OK application/pdf 1838195
09/06-16 HTTP/1.1 200 OK application/pdf 1838195
09/06-16 HTTP/1.1 200 OK application/pdf 1838195
09/06-16 HTTP/1.1 200 OK application/pdf 1838195
09/06-16 HTTP/1.1 200 OK application/pdf 1838195
10/06-16 HTTP/1.1 200 OK application/pdf 1838195
10/06-16 HTTP/1.1 200 OK application/pdf 1838195
10/06-16 HTTP/1.1 200 OK application/pdf 1838195
10/06-16 HTTP/1.1 200 OK application/pdf 1838195
10/06-16 HTTP/1.1 200 OK application/pdf 1838195
10/06-16 HTTP/1.1 200 OK application/pdf 1838195
11/06-16 HTTP/1.1 200 OK application/pdf 1838195
11/06-16 HTTP/1.1 200 OK application/pdf 1838195
11/06-16 HTTP/1.1 200 OK application/pdf 1838195
11/06-16 HTTP/1.1 200 OK application/pdf 1838195
11/06-16 HTTP/1.1 200 OK application/pdf 1838195
12/06-16 HTTP/1.1 200 OK application/pdf 1838195
12/06-16 HTTP/1.1 200 OK application/pdf 1838195
12/06-16 HTTP/1.1 200 OK application/pdf 1838195
12/06-16 HTTP/1.1 200 OK application/pdf 1838195
12/06-16 HTTP/1.1 200 OK application/pdf 1838195
12/06-16 HTTP/1.1 200 OK application/pdf 1838195
13/06-16 HTTP/1.1 200 OK application/pdf 1838195
13/06-16 HTTP/1.1 200 OK application/pdf 1838195
13/06-16 HTTP/1.1 200 OK application/pdf 1838195
13/06-16 HTTP/1.1 200 OK application/pdf 1838195
13/06-16 HTTP/1.1 200 OK application/pdf 1838195
14/06-16 HTTP/1.1 200 OK application/pdf 1838195
14/06-16 HTTP/1.1 200 OK application/pdf 1838195
14/06-16 HTTP/1.1 200 OK application/pdf 1838195
14/06-16 HTTP/1.1 200 OK application/pdf 1838195
14/06-16 HTTP/1.1 200 OK application/pdf 1838195
15/06-16 HTTP/1.1 200 OK application/pdf 1838195
15/06-16 HTTP/1.1 200 OK application/pdf 1838195
15/06-16 HTTP/1.1 200 OK application/pdf 1838195
15/06-16 HTTP/1.1 200 OK application/pdf 1838195
15/06-16 HTTP/1.1 200 OK application/pdf 1838195
16/06-16 HTTP/1.1 200 OK application/pdf 1838195
16/06-16 HTTP/1.1 200 OK application/pdf 1838195
16/06-16 HTTP/1.1 200 OK application/pdf 1838195
16/06-16 HTTP/1.1 200 OK application/pdf 1838195
16/06-16 HTTP/1.1 200 OK application/pdf 1838195
16/06-16 HTTP/1.1 200 OK application/pdf 1838195
17/06-16 HTTP/1.1 200 OK application/pdf 1838195
17/06-16 HTTP/1.1 200 OK application/pdf 1838195
17/06-16 HTTP/1.1 200 OK application/pdf 1838195
17/06-16 HTTP/1.1 200 OK application/pdf 1838195
17/06-16 HTTP/1.1 200 OK application/pdf 1838195
18/06-16 HTTP/1.1 200 OK application/pdf 1838195
18/06-16 HTTP/1.1 200 OK application/pdf 1838195
18/06-16 HTTP/1.1 200 OK application/pdf 1838195
18/06-16 HTTP/1.1 200 OK application/pdf 1838195
18/06-16 HTTP/1.1 200 OK application/pdf 1838195
18/06-16 HTTP/1.1 200 OK application/pdf 1838195
19/06-16 HTTP/1.1 200 OK application/pdf 1838195
19/06-16 HTTP/1.1 200 OK application/pdf 1838195
19/06-16 HTTP/1.1 200 OK application/pdf 1838195
19/06-16 HTTP/1.1 200 OK application/pdf 1838195
19/06-16 HTTP/1.1 200 OK application/pdf 1838195
20/06-16 HTTP/1.1 200 OK application/pdf 1838195
20/06-16 HTTP/1.1 200 OK application/pdf 1838195
20/06-16 HTTP/1.1 200 OK application/pdf 1838195
20/06-16 HTTP/1.1 200 OK application/pdf 1838195
20/06-16 HTTP/1.1 200 OK application/pdf 1838195
21/06-16 HTTP/1.1 200 OK application/pdf 1838195
21/06-16 HTTP/1.1 200 OK application/pdf 1838195
21/06-16 HTTP/1.1 200 OK application/pdf 1838195
21/06-16 HTTP/1.1 200 OK application/pdf 1838195
21/06-16 HTTP/1.1 200 OK application/pdf 1838195
21/06-16 HTTP/1.1 200 OK application/pdf 1838195
22/06-16 HTTP/1.1 200 OK application/pdf 1838195
22/06-16 HTTP/1.1 200 OK application/pdf 1838195
22/06-16 HTTP/1.1 200 OK application/pdf 1838195
22/06-16 HTTP/1.1 200 OK application/pdf 1838195
22/06-16 HTTP/1.1 200 OK application/pdf 1838195
23/06-16 HTTP/1.1 200 OK application/pdf 1838195
23/06-16 HTTP/1.1 200 OK application/pdf 1838195
23/06-16 HTTP/1.1 200 OK application/pdf 1838195
23/06-16 HTTP/1.1 200 OK application/pdf 1838195
23/06-16 HTTP/1.1 200 OK application/pdf 1838195
23/06-16 HTTP/1.1 200 OK application/pdf 1838195
24/06-16 HTTP/1.1 200 OK application/pdf 1838195
24/06-16 HTTP/1.1 200 OK application/pdf 1838195
24/06-16 HTTP/1.1 200 OK application/pdf 1838195
24/06-16 HTTP/1.1 200 OK application/pdf 1838195
24/06-16 HTTP/1.1 200 OK application/pdf 1838195
25/06-16 HTTP/1.1 200 OK application/pdf 1838195
25/06-16 HTTP/1.1 200 OK application/pdf 1838195
25/06-16 HTTP/1.1 200 OK application/pdf 1838195
25/06-16 HTTP/1.1 200 OK application/pdf 1838195
25/06-16 HTTP/1.1 200 OK application/pdf 1838195
26/06-16 HTTP/1.1 200 OK application/pdf 1838195
26/06-16 HTTP/1.1 200 OK application/pdf 1838195
26/06-16 HTTP/1.1 200 OK application/pdf 1838195
26/06-16 HTTP/1.1 200 OK application/pdf 1838195
26/06-16 HTTP/1.1 200 OK application/pdf 1838195
26/06-16 HTTP/1.1 200 OK application/pdf 1838195
27/06-16 HTTP/1.1 200 OK application/pdf 1838195
27/06-16 HTTP/1.1 200 OK application/pdf 1838195
27/06-16 HTTP/1.1 200 OK application/pdf 1838195
27/06-16 HTTP/1.1 200 OK application/pdf 1838195
27/06-16 HTTP/1.1 200 OK application/pdf 1838195
28/06-16 HTTP/1.1 200 OK application/pdf 1838195
28/06-16 HTTP/1.1 200 OK application/pdf 1838195
28/06-16 HTTP/1.1 200 OK application/pdf 1838195
28/06-16 HTTP/1.1 200 OK application/pdf 1838195
28/06-16 HTTP/1.1 200 OK application/pdf 1838195
29/06-16 HTTP/1.1 200 OK application/pdf 1838195
29/06-16 HTTP/1.1 200 OK application/pdf 1838195
29/06-16 HTTP/1.1 200 OK application/pdf 1838195
29/06-16 HTTP/1.1 200 OK application/pdf 1838195
29/06-16 HTTP/1.1 200 OK application/pdf 1838195
29/06-16 HTTP/1.1 200 OK application/pdf 1838195
30/06-16 HTTP/1.1 200 OK application/pdf 1838195
30/06-16 HTTP/1.1 200 OK application/pdf 1838195
30/06-16 HTTP/1.1 200 OK application/pdf 1838195
30/06-16 HTTP/1.1 200 OK application/pdf 1838195
30/06-16 HTTP/1.1 200 OK application/pdf 1838195
01/07-16 HTTP/1.1 200 OK application/pdf 1838195
01/07-16 HTTP/1.1 200 OK application/pdf 1838195
01/07-16 HTTP/1.1 200 OK application/pdf 1838195
01/07-16 HTTP/1.1 200 OK application/pdf 1838195
01/07-16 HTTP/1.1 200 OK application/pdf 1838195
02/07-16 HTTP/1.1 200 OK application/pdf 1838195
02/07-16 HTTP/1.1 200 OK application/pdf 1838195
02/07-16 HTTP/1.1 200 OK application/pdf 1838195
02/07-16 HTTP/1.1 200 OK application/pdf 1838195
02/07-16 HTTP/1.1 200 OK application/pdf 1838195
02/07-16 HTTP/1.1 200 OK application/pdf 1838195
03/07-16 HTTP/1.1 200 OK application/pdf 1838195
03/07-16 HTTP/1.1 200 OK application/pdf 1838195
03/07-16 HTTP/1.1 200 OK application/pdf 1838195
03/07-16 HTTP/1.1 200 OK application/pdf 1838195
03/07-16 HTTP/1.1 200 OK application/pdf 1838195
04/07-16 HTTP/1.1 200 OK application/pdf 1838195
04/07-16 HTTP/1.1 200 OK application/pdf 1838195
04/07-16 HTTP/1.1 200 OK application/pdf 1838195
04/07-16 HTTP/1.1 200 OK application/pdf 1838195
04/07-16 HTTP/1.1 200 OK application/pdf 1838195
05/07-16 HTTP/1.1 200 OK application/pdf 1838195
05/07-16 HTTP/1.1 200 OK application/pdf 1838195
05/07-16 HTTP/1.1 200 OK application/pdf 1838195
05/07-16 HTTP/1.1 200 OK application/pdf 1838195
05/07-16 HTTP/1.1 200 OK application/pdf 1838195
05/07-16 HTTP/1.1 200 OK application/pdf 1838195
06/07-16 HTTP/1.1 200 OK application/pdf 1838195
06/07-16 HTTP/1.1 200 OK application/pdf 1838195
06/07-16 HTTP/1.1 200 OK application/pdf 1838195
06/07-16 HTTP/1.1 200 OK application/pdf 1838195
06/07-16 HTTP/1.1 200 OK application/pdf 1838195
07/07-16 HTTP/1.1 200 OK application/pdf 1838195
07/07-16 HTTP/1.1 200 OK application/pdf 1838195
07/07-16 HTTP/1.1 200 OK application/pdf 1838195
07/07-16 HTTP/1.1 200 OK application/pdf 1838195
07/07-16 HTTP/1.1 200 OK application/pdf 1838195
08/07-16 HTTP/1.1 200 OK application/pdf 1838195
08/07-16 HTTP/1.1 200 OK application/pdf 1838195
08/07-16 HTTP/1.1 200 OK application/pdf 1838195
08/07-16 HTTP/1.1 200 OK application/pdf 1838195
08/07-16 HTTP/1.1 200 OK application/pdf 1838195
09/07-16 HTTP/1.1 200 OK application/pdf 1838195
09/07-16 HTTP/1.1 200 OK application/pdf 1838195
09/07-16 HTTP/1.1 200 OK application/pdf 1838195
09/07-16 HTTP/1.1 200 OK application/pdf 1838195
09/07-16 HTTP/1.1 200 OK application/pdf 1838195
09/07-16 HTTP/1.1 200 OK application/pdf 1838195
10/07-16 HTTP/1.1 200 OK application/pdf 1838195
10/07-16 HTTP/1.1 200 OK application/pdf 1838195
10/07-16 HTTP/1.1 200 OK application/pdf 1838195
10/07-16 HTTP/1.1 200 OK application/pdf 1838195
10/07-16 HTTP/1.1 200 OK application/pdf 1838195
11/07-16 HTTP/1.1 200 OK application/pdf 1838195
11/07-16 HTTP/1.1 200 OK application/pdf 1838195
11/07-16 HTTP/1.1 200 OK application/pdf 1838195
11/07-16 HTTP/1.1 200 OK application/pdf 1838195
11/07-16 HTTP/1.1 200 OK application/pdf 1838195
11/07-16 HTTP/1.1 200 OK application/pdf 1838195
12/07-16 HTTP/1.1 200 OK application/pdf 1838195
12/07-16 HTTP/1.1 200 OK application/pdf 1838195
12/07-16 HTTP/1.1 200 OK application/pdf 1838195
12/07-16 HTTP/1.1 200 OK application/pdf 1838195
12/07-16 HTTP/1.1 200 OK application/pdf 1838195
13/07-16 HTTP/1.1 200 OK application/pdf 1838195
13/07-16 HTTP/1.1 200 OK application/pdf 1838195
13/07-16 HTTP/1.1 200 OK application/pdf 1838195
13/07-16 HTTP/1.1 200 OK application/pdf 1838195
13/07-16 HTTP/1.1 200 OK application/pdf 1838195
13/07-16 HTTP/1.1 200 OK application/pdf 1838195
14/07-16 HTTP/1.1 200 OK application/pdf 1838195
14/07-16 HTTP/1.1 200 OK application/pdf 1838195
14/07-16 HTTP/1.1 200 OK application/pdf 1838195
14/07-16 HTTP/1.1 200 OK application/pdf 1838195
15/07-16 HTTP/1.1 200 OK application/pdf 1838195
15/07-16 HTTP/1.1 200 OK application/pdf 1838195
15/07-16 HTTP/1.1 200 OK application/pdf 1838195
15/07-16 HTTP/1.1 200 OK application/pdf 1838195
15/07-16 HTTP/1.1 200 OK application/pdf 1838195
16/07-16 HTTP/1.1 200 OK application/pdf 1838195
16/07-16 HTTP/1.1 200 OK application/pdf 1838195
16/07-16 HTTP/1.1 200 OK application/pdf 1838195
16/07-16 HTTP/1.1 200 OK application/pdf 1838195
16/07-16 HTTP/1.1 200 OK application/pdf 1838195
17/07-16 HTTP/1.1 200 OK application/pdf 1838195
17/07-16 HTTP/1.1 200 OK application/pdf 1838195
17/07-16 HTTP/1.1 200 OK application/pdf 1838195
17/07-16 HTTP/1.1 200 OK application/pdf 1838195
17/07-16 HTTP/1.1 200 OK application/pdf 1838195
18/07-16 HTTP/1.1 200 OK application/pdf 1838195
18/07-16 HTTP/1.1 200 OK application/pdf 1838195
18/07-16 HTTP/1.1 200 OK application/pdf 1838195
18/07-16 HTTP/1.1 200 OK application/pdf 1838195
18/07-16 HTTP/1.1 200 OK application/pdf 1838195
18/07-16 HTTP/1.1 200 OK application/pdf 1838195
19/07-16 HTTP/1.1 200 OK application/pdf 1838195
19/07-16 HTTP/1.1 200 OK application/pdf 1838195
19/07-16 HTTP/1.1 200 OK application/pdf 1838195
19/07-16 HTTP/1.1 200 OK application/pdf 1838195
19/07-16 HTTP/1.1 200 OK application/pdf 1838195
20/07-16 HTTP/1.1 200 OK application/pdf 1838195
20/07-16 HTTP/1.1 200 OK application/pdf 1838195
20/07-16 HTTP/1.1 200 OK application/pdf 1838195
20/07-16 HTTP/1.1 200 OK application/pdf 1838195
20/07-16 HTTP/1.1 200 OK application/pdf 1838195
21/07-16 HTTP/1.1 200 OK application/pdf 1838195
21/07-16 HTTP/1.1 200 OK application/pdf 1838195
21/07-16 HTTP/1.1 200 OK application/pdf 1838195
21/07-16 HTTP/1.1 200 OK application/pdf 1838195
21/07-16 HTTP/1.1 200 OK application/pdf 1838195
22/07-16 HTTP/1.1 200 OK application/pdf 1838195
22/07-16 HTTP/1.1 200 OK application/pdf 1838195
22/07-16 HTTP/1.1 200 OK application/pdf 1838195
22/07-16 HTTP/1.1 200 OK application/pdf 1838195
22/07-16 HTTP/1.1 200 OK application/pdf 1838195
23/07-16 HTTP/1.1 200 OK application/pdf 1838195
23/07-16 HTTP/1.1 200 OK application/pdf 1838195
23/07-16 HTTP/1.1 200 OK application/pdf 1838195
23/07-16 HTTP/1.1 200 OK application/pdf 1838195
23/07-16 HTTP/1.1 200 OK application/pdf 1838195
24/07-16 HTTP/1.1 200 OK application/pdf 1838195
24/07-16 HTTP/1.1 200 OK application/pdf 1838195
24/07-16 HTTP/1.1 200 OK application/pdf 1838195
24/07-16 HTTP/1.1 200 OK application/pdf 1838195
24/07-16 HTTP/1.1 200 OK application/pdf 1838195
25/07-16 HTTP/1.1 200 OK application/pdf 1838195
25/07-16 HTTP/1.1 200 OK application/pdf 1838195
25/07-16 HTTP/1.1 200 OK application/pdf 1838195
25/07-16 HTTP/1.1 200 OK application/pdf 1838195
25/07-16 HTTP/1.1 200 OK application/pdf 1838195
26/07-16 HTTP/1.1 200 OK application/pdf 1838195
26/07-16 HTTP/1.1 200 OK application/pdf 1838195
26/07-16 HTTP/1.1 200 OK application/pdf 1838195
26/07-16 HTTP/1.1 200 OK application/pdf 1838195
26/07-16 HTTP/1.1 200 OK application/pdf 1838195
26/07-16 HTTP/1.1 200 OK application/pdf 1838195
27/07-16 HTTP/1.1 200 OK application/pdf 1838195
27/07-16 HTTP/1.1 200 OK application/pdf 1838195
27/07-16 HTTP/1.1 200 OK application/pdf 1838195
27/07-16 HTTP/1.1 200 OK application/pdf 1838195
27/07-16 HTTP/1.1 200 OK application/pdf 1838195
28/07-16 HTTP/1.1 200 OK application/pdf 1838195
28/07-16 HTTP/1.1 200 OK application/pdf 1838195
28/07-16 HTTP/1.1 200 OK application/pdf 1838195
28/07-16 HTTP/1.1 200 OK application/pdf 1838195
29/07-16 HTTP/1.1 200 OK application/pdf 1838195
29/07-16 HTTP/1.1 200 OK application/pdf 1838195
29/07-16 HTTP/1.1 200 OK application/pdf 1838195
29/07-16 HTTP/1.1 200 OK application/pdf 1838195
29/07-16 HTTP/1.1 200 OK application/pdf 1838195
29/07-16 HTTP/1.1 200 OK application/pdf 1838195
30/07-16 HTTP/1.1 200 OK application/pdf 1838195
30/07-16 HTTP/1.1 200 OK application/pdf 1838195
30/07-16 HTTP/1.1 200 OK application/pdf 1838195
30/07-16 HTTP/1.1 200 OK application/pdf 1838195
31/07-16 HTTP/1.1 200 OK application/pdf 1838195
31/07-16 HTTP/1.1 200 OK application/pdf 1838195
31/07-16 HTTP/1.1 200 OK application/pdf 1838195
31/07-16 HTTP/1.1 200 OK application/pdf 1838195
31/07-16 HTTP/1.1 200 OK application/pdf 1838195
31/07-16 HTTP/1.1 200 OK application/pdf 1838195
01/08-16 HTTP/1.1 200 OK application/pdf 1838195
01/08-16 HTTP/1.1 200 OK application/pdf 1838195
01/08-16 HTTP/1.1 200 OK application/pdf 1838195
01/08-16 HTTP/1.1 200 OK application/pdf 1838195
01/08-16 HTTP/1.1 200 OK application/pdf 1838195
02/08-16 HTTP/1.1 200 OK application/pdf 1838195
02/08-16 HTTP/1.1 200 OK application/pdf 1838195
02/08-16 HTTP/1.1 200 OK application/pdf 1838195
02/08-16 HTTP/1.1 200 OK application/pdf 1838195
03/08-16 HTTP/1.1 200 OK application/pdf 1838195
03/08-16 HTTP/1.1 200 OK application/pdf 1838195
03/08-16 HTTP/1.1 200 OK application/pdf 1838195
03/08-16 HTTP/1.1 200 OK application/pdf 1838195
03/08-16 HTTP/1.1 200 OK application/pdf 1838195
04/08-16 HTTP/1.1 200 OK application/pdf 1838195
04/08-16 HTTP/1.1 200 OK application/pdf 1838195
05/08-16 HTTP/1.1 200 OK application/pdf 1838195
06/08-16 HTTP/1.1 200 OK application/pdf 1838195
06/08-16 HTTP/1.1 200 OK application/pdf 1838195
06/08-16 HTTP/1.1 200 OK application/pdf 1838195
07/08-16 HTTP/1.1 200 OK application/pdf 1838195
07/08-16 HTTP/1.1 200 OK application/pdf 1838195
08/08-16 HTTP/1.1 200 OK application/pdf 1838195
08/08-16 HTTP/1.1 200 OK application/pdf 1838195
09/08-16 HTTP/1.1 200 OK application/pdf 1838195
10/08-16 HTTP/1.1 200 OK application/pdf 1838195
11/08-16 HTTP/1.1 200 OK application/pdf 1838195
11/08-16 HTTP/1.1 200 OK application/pdf 1838195
12/08-16 HTTP/1.1 200 OK application/pdf 1838195
12/08-16 HTTP/1.1 200 OK application/pdf 1838195
13/08-16 HTTP/1.1 200 OK application/pdf 1838195
13/08-16 HTTP/1.1 200 OK application/pdf 1838195
13/08-16 HTTP/1.1 200 OK application/pdf 1838195
13/08-16 HTTP/1.1 200 OK application/pdf 1838195
14/08-16 HTTP/1.1 200 OK application/pdf 1838195
14/08-16 HTTP/1.1 200 OK application/pdf 1838195
14/08-16 HTTP/1.1 200 OK application/pdf 1838195
14/08-16 HTTP/1.1 200 OK application/pdf 1838195
15/08-16 HTTP/1.1 200 OK application/pdf 1838195
15/08-16 HTTP/1.1 200 OK application/pdf 1838195
15/08-16 HTTP/1.1 200 OK application/pdf 1838195
15/08-16 HTTP/1.1 200 OK application/pdf 1838195
15/08-16 HTTP/1.1 200 OK application/pdf 1838195
16/08-16 HTTP/1.1 200 OK application/pdf 1838195
16/08-16 HTTP/1.1 200 OK application/pdf 1838195
16/08-16 HTTP/1.1 200 OK application/pdf 1838195
16/08-16 HTTP/1.1 200 OK application/pdf 1838195
17/08-16 HTTP/1.1 200 OK application/pdf 1838195
17/08-16 HTTP/1.1 200 OK application/pdf 1838195
17/08-16 HTTP/1.1 200 OK application/pdf 1838195
17/08-16 HTTP/1.1 200 OK application/pdf 1838195
17/08-16 HTTP/1.1 200 OK application/pdf 1838195
18/08-16 HTTP/1.1 200 OK application/pdf 1838195
18/08-16 HTTP/1.1 200 OK application/pdf 1838195
18/08-16 HTTP/1.1 200 OK application/pdf 1838195
18/08-16 HTTP/1.1 200 OK application/pdf 1838195
18/08-16 HTTP/1.1 200 OK application/pdf 1838195
19/08-16 HTTP/1.1 200 OK application/pdf 1838195
19/08-16 HTTP/1.1 200 OK application/pdf 1838195
19/08-16 HTTP/1.1 200 OK application/pdf 1838195
19/08-16 HTTP/1.1 200 OK application/pdf 1838195
19/08-16 HTTP/1.1 200 OK application/pdf 1838195
20/08-16 HTTP/1.1 200 OK application/pdf 1838195
20/08-16 HTTP/1.1 200 OK application/pdf 1838195
20/08-16 HTTP/1.1 200 OK application/pdf 1838195
20/08-16 HTTP/1.1 200 OK application/pdf 1838195
20/08-16 HTTP/1.1 200 OK application/pdf 1838195
21/08-16 HTTP/1.1 200 OK application/pdf 1838195
21/08-16 HTTP/1.1 200 OK application/pdf 1838195
21/08-16 HTTP/1.1 200 OK application/pdf 1838195
21/08-16 HTTP/1.1 200 OK application/pdf 1838195
21/08-16 HTTP/1.1 200 OK application/pdf 1838195
22/08-16 HTTP/1.1 200 OK application/pdf 1838195
22/08-16 HTTP/1.1 200 OK application/pdf 1838195
22/08-16 HTTP/1.1 200 OK application/pdf 1838195
22/08-16 HTTP/1.1 200 OK application/pdf 1838195
22/08-16 HTTP/1.1 200 OK application/pdf 1838195
23/08-16 HTTP/1.1 200 OK application/pdf 1838195
23/08-16 HTTP/1.1 200 OK application/pdf 1838195
23/08-16 HTTP/1.1 200 OK application/pdf 1838195
23/08-16 HTTP/1.1 200 OK application/pdf 1838195
23/08-16 HTTP/1.1 200 OK application/pdf 1838195
24/08-16 HTTP/1.1 200 OK application/pdf 1838195
24/08-16 HTTP/1.1 200 OK application/pdf 1838195
24/08-16 HTTP/1.1 200 OK application/pdf 1838195
24/08-16 HTTP/1.1 200 OK application/pdf 1838195
25/08-16 HTTP/1.1 200 OK application/pdf 1838195
25/08-16 HTTP/1.1 200 OK application/pdf 1838195
25/08-16 HTTP/1.1 200 OK application/pdf 1838195
25/08-16 HTTP/1.1 200 OK application/pdf 1838195
25/08-16 HTTP/1.1 200 OK application/pdf 1838195
26/08-16 HTTP/1.1 200 OK application/pdf 1838195
26/08-16 HTTP/1.1 200 OK application/pdf 1838195
26/08-16 HTTP/1.1 200 OK application/pdf 1838195
26/08-16 HTTP/1.1 200 OK application/pdf 1838195
26/08-16 HTTP/1.1 200 OK application/pdf 1838195
27/08-16 HTTP/1.1 200 OK application/pdf 1838195
27/08-16 HTTP/1.1 200 OK application/pdf 1838195
27/08-16 HTTP/1.1 200 OK application/pdf 1838195
27/08-16 HTTP/1.1 200 OK application/pdf 1838195
28/08-16 HTTP/1.1 200 OK application/pdf 1838195
28/08-16 HTTP/1.1 200 OK application/pdf 1838195
28/08-16 HTTP/1.1 200 OK application/pdf 1838195
28/08-16 HTTP/1.1 200 OK application/pdf 1838195
28/08-16 HTTP/1.1 200 OK application/pdf 1838195
29/08-16 HTTP/1.1 200 OK application/pdf 1838195
29/08-16 HTTP/1.1 200 OK application/pdf 1838195
29/08-16 HTTP/1.1 200 OK application/pdf 1838195
29/08-16 HTTP/1.1 200 OK application/pdf 1838195
29/08-16 HTTP/1.1 200 OK application/pdf 1838195
30/08-16 HTTP/1.1 200 OK application/pdf 1838195
30/08-16 HTTP/1.1 200 OK application/pdf 1838195
30/08-16 HTTP/1.1 200 OK application/pdf 1838195
30/08-16 HTTP/1.1 200 OK application/pdf 1838195
30/08-16 HTTP/1.1 200 OK application/pdf 1838195
31/08-16 HTTP/1.1 200 OK application/pdf 1838195
31/08-16 HTTP/1.1 200 OK application/pdf 1838195
31/08-16 HTTP/1.1 200 OK application/pdf 1838195
31/08-16 HTTP/1.1 200 OK application/pdf 1838195
01/09-16 HTTP/1.1 200 OK application/pdf 1838195
01/09-16 HTTP/1.1 200 OK application/pdf 1838195
01/09-16 HTTP/1.1 200 OK application/pdf 1838195
01/09-16 HTTP/1.1 200 OK application/pdf 1838195
01/09-16 HTTP/1.1 200 OK application/pdf 1838195
02/09-16 HTTP/1.1 200 OK application/pdf 1838195
02/09-16 HTTP/1.1 200 OK application/pdf 1838195
02/09-16 HTTP/1.1 200 OK application/pdf 1838195
02/09-16 HTTP/1.1 200 OK application/pdf 1838195
02/09-16 HTTP/1.1 200 OK application/pdf 1838195
03/09-16 HTTP/1.1 200 OK application/pdf 1838195
03/09-16 HTTP/1.1 200 OK application/pdf 1838195
03/09-16 HTTP/1.1 200 OK application/pdf 1838195
03/09-16 HTTP/1.1 200 OK application/pdf 1838195
03/09-16 HTTP/1.1 200 OK application/pdf 1838195
03/09-16 HTTP/1.1 200 OK application/pdf 1838195
04/09-16 HTTP/1.1 200 OK application/pdf 1838195
04/09-16 HTTP/1.1 200 OK application/pdf 1838195
04/09-16 HTTP/1.1 200 OK application/pdf 1838195
04/09-16 HTTP/1.1 200 OK application/pdf 1838195
04/09-16 HTTP/1.1 200 OK application/pdf 1838195
05/09-16 N/A 0
05/09-16 HTTP/1.1 200 OK application/pdf 1838195
05/09-16 HTTP/1.1 200 OK application/pdf 1838195
05/09-16 HTTP/1.1 200 OK application/pdf 1838195
06/09-16 HTTP/1.1 200 OK application/pdf 1838195
06/09-16 HTTP/1.1 200 OK application/pdf 1838195
06/09-16 HTTP/1.1 200 OK application/pdf 1838195
06/09-16 HTTP/1.1 200 OK application/pdf 1838195
06/09-16 HTTP/1.1 200 OK application/pdf 1838195
07/09-16 HTTP/1.1 200 OK application/pdf 1838195
07/09-16 HTTP/1.1 200 OK application/pdf 1838195
07/09-16 HTTP/1.1 200 OK application/pdf 1838195
07/09-16 HTTP/1.1 200 OK application/pdf 1838195
07/09-16 HTTP/1.1 200 OK application/pdf 1838195
08/09-16 HTTP/1.1 200 OK application/pdf 1838195
08/09-16 HTTP/1.1 200 OK application/pdf 1838195
08/09-16 HTTP/1.1 200 OK application/pdf 1838195
08/09-16 HTTP/1.1 200 OK application/pdf 1838195
08/09-16 HTTP/1.1 200 OK application/pdf 1838195
09/09-16 HTTP/1.1 200 OK application/pdf 1838195
09/09-16 HTTP/1.1 200 OK application/pdf 1838195
09/09-16 HTTP/1.1 200 OK application/pdf 1838195
09/09-16 HTTP/1.1 200 OK application/pdf 1838195
09/09-16 HTTP/1.1 200 OK application/pdf 1838195
10/09-16 N/A 0
10/09-16 HTTP/1.1 200 OK application/pdf 1838195
10/09-16 HTTP/1.1 200 OK application/pdf 1838195
10/09-16 HTTP/1.1 200 OK application/pdf 1838195
11/09-16 HTTP/1.1 200 OK application/pdf 1838195
11/09-16 HTTP/1.1 200 OK application/pdf 1838195
11/09-16 HTTP/1.1 200 OK application/pdf 1838195
11/09-16 HTTP/1.1 200 OK application/pdf 1838195
11/09-16 HTTP/1.1 200 OK application/pdf 1838195
12/09-16 HTTP/1.1 200 OK application/pdf 1838195
12/09-16 HTTP/1.1 200 OK application/pdf 1838195
12/09-16 HTTP/1.1 200 OK application/pdf 1838195
12/09-16 HTTP/1.1 200 OK application/pdf 1838195
12/09-16 HTTP/1.1 200 OK application/pdf 1838195
13/09-16 HTTP/1.1 200 OK application/pdf 1838195
13/09-16 HTTP/1.1 200 OK application/pdf 1838195
13/09-16 HTTP/1.1 200 OK application/pdf 1838195
13/09-16 HTTP/1.1 200 OK application/pdf 1838195
14/09-16 HTTP/1.1 200 OK application/pdf 1838195
14/09-16 HTTP/1.1 200 OK application/pdf 1838195
14/09-16 HTTP/1.1 200 OK application/pdf 1838195
14/09-16 HTTP/1.1 200 OK application/pdf 1838195
14/09-16 HTTP/1.1 200 OK application/pdf 1838195
15/09-16 HTTP/1.1 200 OK application/pdf 1838195
15/09-16 HTTP/1.1 200 OK application/pdf 1838195
15/09-16 HTTP/1.1 200 OK application/pdf 1838195
15/09-16 HTTP/1.1 200 OK application/pdf 1838195
15/09-16 HTTP/1.1 200 OK application/pdf 1838195
16/09-16 HTTP/1.1 200 OK application/pdf 1838195
16/09-16 HTTP/1.1 200 OK application/pdf 1838195
16/09-16 HTTP/1.1 200 OK application/pdf 1838195
16/09-16 HTTP/1.1 200 OK application/pdf 1838195
16/09-16 HTTP/1.1 200 OK application/pdf 1838195
17/09-16 HTTP/1.1 200 OK application/pdf 1838195
17/09-16 HTTP/1.1 200 OK application/pdf 1838195
17/09-16 HTTP/1.1 200 OK application/pdf 1838195
17/09-16 HTTP/1.1 200 OK application/pdf 1838195
18/09-16 HTTP/1.1 200 OK application/pdf 1838195
18/09-16 HTTP/1.1 200 OK application/pdf 1838195
18/09-16 HTTP/1.1 200 OK application/pdf 1838195
18/09-16 HTTP/1.1 200 OK application/pdf 1838195
18/09-16 HTTP/1.1 200 OK application/pdf 1838195
19/09-16 HTTP/1.1 200 OK application/pdf 1838195
19/09-16 HTTP/1.1 200 OK application/pdf 1838195
19/09-16 HTTP/1.1 200 OK application/pdf 1838195
19/09-16 HTTP/1.1 200 OK application/pdf 1838195
20/09-16 HTTP/1.1 200 OK application/pdf 1838195
20/09-16 HTTP/1.1 200 OK application/pdf 1838195
20/09-16 HTTP/1.1 200 OK application/pdf 1838195
20/09-16 HTTP/1.1 200 OK application/pdf 1838195
20/09-16 HTTP/1.1 200 OK application/pdf 1838195
21/09-16 HTTP/1.1 200 OK application/pdf 1838195
21/09-16 HTTP/1.1 200 OK application/pdf 1838195
21/09-16 HTTP/1.1 200 OK application/pdf 1838195
21/09-16 HTTP/1.1 200 OK application/pdf 1838195
22/09-16 HTTP/1.1 200 OK application/pdf 1838195
22/09-16 HTTP/1.1 200 OK application/pdf 1838195
22/09-16 HTTP/1.1 200 OK application/pdf 1838195
22/09-16 HTTP/1.1 200 OK application/pdf 1838195
22/09-16 HTTP/1.1 200 OK application/pdf 1838195
23/09-16 HTTP/1.1 200 OK application/pdf 1838195
23/09-16 HTTP/1.1 200 OK application/pdf 1838195
23/09-16 HTTP/1.1 200 OK application/pdf 1838195
24/09-16 HTTP/1.1 200 OK application/pdf 1838195
24/09-16 HTTP/1.1 200 OK application/pdf 1838195
24/09-16 HTTP/1.1 200 OK application/pdf 1838195
24/09-16 HTTP/1.1 200 OK application/pdf 1838195
25/09-16 HTTP/1.1 200 OK application/pdf 1838195
25/09-16 HTTP/1.1 200 OK application/pdf 1838195
25/09-16 HTTP/1.1 200 OK application/pdf 1838195
25/09-16 HTTP/1.1 200 OK application/pdf 1838195
25/09-16 HTTP/1.1 200 OK application/pdf 1838195
26/09-16 HTTP/1.1 200 OK application/pdf 1838195
26/09-16 HTTP/1.1 200 OK application/pdf 1838195
26/09-16 HTTP/1.1 200 OK application/pdf 1838195
26/09-16 HTTP/1.1 200 OK application/pdf 1838195
27/09-16 HTTP/1.1 200 OK application/pdf 1838195
27/09-16 HTTP/1.1 200 OK application/pdf 1838195
27/09-16 HTTP/1.1 200 OK application/pdf 1838195
27/09-16 HTTP/1.1 200 OK application/pdf 1838195
28/09-16 HTTP/1.1 200 OK application/pdf 1838195
28/09-16 HTTP/1.1 200 OK application/pdf 1838195
28/09-16 HTTP/1.1 200 OK application/pdf 1838195
28/09-16 HTTP/1.1 200 OK application/pdf 1838195
28/09-16 HTTP/1.1 200 OK application/pdf 1838195
29/09-16 HTTP/1.1 200 OK application/pdf 1838195
29/09-16 HTTP/1.1 200 OK application/pdf 1838195
29/09-16 HTTP/1.1 200 OK application/pdf 1838195
29/09-16 HTTP/1.1 200 OK application/pdf 1838195
30/09-16 HTTP/1.1 200 OK application/pdf 1838195
30/09-16 HTTP/1.1 200 OK application/pdf 1838195
30/09-16 HTTP/1.1 200 OK application/pdf 1838195
30/09-16 HTTP/1.1 200 OK application/pdf 1838195
01/10-16 HTTP/1.1 200 OK application/pdf 1838195
01/10-16 HTTP/1.1 200 OK application/pdf 1838195
01/10-16 HTTP/1.1 200 OK application/pdf 1838195
01/10-16 HTTP/1.1 200 OK application/pdf 1838195
01/10-16 HTTP/1.1 200 OK application/pdf 1838195
02/10-16 HTTP/1.1 200 OK application/pdf 1838195
02/10-16 HTTP/1.1 200 OK application/pdf 1838195
02/10-16 HTTP/1.1 200 OK application/pdf 1838195
02/10-16 HTTP/1.1 200 OK application/pdf 1838195
03/10-16 HTTP/1.1 200 OK application/pdf 1838195
03/10-16 HTTP/1.1 200 OK application/pdf 1838195
03/10-16 HTTP/1.1 200 OK application/pdf 1838195
03/10-16 HTTP/1.1 200 OK application/pdf 1838195
03/10-16 HTTP/1.1 200 OK application/pdf 1838195
04/10-16 HTTP/1.1 200 OK application/pdf 1838195
04/10-16 HTTP/1.1 200 OK application/pdf 1838195
04/10-16 HTTP/1.1 200 OK application/pdf 1838195
04/10-16 HTTP/1.1 200 OK application/pdf 1838195
05/10-16 HTTP/1.1 200 OK application/pdf 1838195
05/10-16 HTTP/1.1 200 OK application/pdf 1838195
05/10-16 HTTP/1.1 200 OK application/pdf 1838195
05/10-16 HTTP/1.1 200 OK application/pdf 1838195
06/10-16 HTTP/1.1 200 OK application/pdf 1838195
06/10-16 HTTP/1.1 200 OK application/pdf 1838195
06/10-16 HTTP/1.1 200 OK application/pdf 1838195
07/10-16 HTTP/1.1 200 OK application/pdf 1838195
07/10-16 HTTP/1.1 200 OK application/pdf 1838195
07/10-16 HTTP/1.1 200 OK application/pdf 1838195
07/10-16 HTTP/1.1 200 OK application/pdf 1838195
08/10-16 N/A 0
08/10-16 HTTP/1.1 200 OK application/pdf 1838195
08/10-16 HTTP/1.1 200 OK application/pdf 1838195
09/10-16 HTTP/1.1 200 OK application/pdf 1838195
09/10-16 HTTP/1.1 200 OK application/pdf 1838195
09/10-16 HTTP/1.1 200 OK application/pdf 1838195
09/10-16 HTTP/1.1 200 OK application/pdf 1838195
10/10-16 HTTP/1.1 200 OK application/pdf 1838195
10/10-16 HTTP/1.1 200 OK application/pdf 1838195
10/10-16 HTTP/1.1 200 OK application/pdf 1838195
10/10-16 HTTP/1.1 200 OK application/pdf 1838195
11/10-16 HTTP/1.1 200 OK application/pdf 1838195
11/10-16 HTTP/1.1 200 OK application/pdf 1838195
11/10-16 HTTP/1.1 200 OK application/pdf 1838195
11/10-16 HTTP/1.1 200 OK application/pdf 1838195
12/10-16 HTTP/1.1 200 OK application/pdf 1838195
12/10-16 HTTP/1.1 200 OK application/pdf 1838195
12/10-16 HTTP/1.1 200 OK application/pdf 1838195
12/10-16 HTTP/1.1 200 OK application/pdf 1838195
12/10-16 HTTP/1.1 200 OK application/pdf 1838195
13/10-16 N/A 0
13/10-16 HTTP/1.1 200 OK application/pdf 1838195
13/10-16 HTTP/1.1 200 OK application/pdf 1838195
14/10-16 HTTP/1.1 200 OK application/pdf 1838195
14/10-16 HTTP/1.1 200 OK application/pdf 1838195
14/10-16 HTTP/1.1 200 OK application/pdf 1838195
14/10-16 HTTP/1.1 200 OK application/pdf 1838195
15/10-16 HTTP/1.1 200 OK application/pdf 1838195
15/10-16 HTTP/1.1 200 OK application/pdf 1838195
15/10-16 HTTP/1.1 200 OK application/pdf 1838195
15/10-16 HTTP/1.1 200 OK application/pdf 1838195
16/10-16 N/A 0
16/10-16 HTTP/1.1 200 OK application/pdf 1838195
16/10-16 HTTP/1.1 200 OK application/pdf 1838195
16/10-16 HTTP/1.1 200 OK application/pdf 1838195
17/10-16 HTTP/1.1 200 OK application/pdf 1838195
17/10-16 HTTP/1.1 200 OK application/pdf 1838195
17/10-16 HTTP/1.1 200 OK application/pdf 1838195
18/10-16 HTTP/1.1 200 OK application/pdf 1838195
18/10-16 HTTP/1.1 200 OK application/pdf 1838195
18/10-16 HTTP/1.1 200 OK application/pdf 1838195
18/10-16 HTTP/1.1 200 OK application/pdf 1838195
19/10-16 HTTP/1.1 200 OK application/pdf 1838195
19/10-16 HTTP/1.1 200 OK application/pdf 1838195
19/10-16 HTTP/1.1 200 OK application/pdf 1838195
19/10-16 HTTP/1.1 200 OK application/pdf 1838195
20/10-16 HTTP/1.1 200 OK application/pdf 1838195
20/10-16 HTTP/1.1 200 OK application/pdf 1838195
20/10-16 HTTP/1.1 200 OK application/pdf 1838195
21/10-16 HTTP/1.1 200 OK application/pdf 1838195
21/10-16 HTTP/1.1 200 OK application/pdf 1838195
21/10-16 HTTP/1.1 200 OK application/pdf 1838195
22/10-16 HTTP/1.1 200 OK application/pdf 1838195
22/10-16 HTTP/1.1 200 OK application/pdf 1838195
22/10-16 HTTP/1.1 200 OK application/pdf 1838195
22/10-16 HTTP/1.1 200 OK application/pdf 1838195
23/10-16 HTTP/1.1 200 OK application/pdf 1838195
23/10-16 HTTP/1.1 200 OK application/pdf 1838195
23/10-16 HTTP/1.1 200 OK application/pdf 1838195
23/10-16 HTTP/1.1 200 OK application/pdf 1838195
23/10-16 HTTP/1.1 200 OK application/pdf 1838195
24/10-16 HTTP/1.1 200 OK application/pdf 1838195
25/10-16 HTTP/1.1 200 OK application/pdf 1838195
25/10-16 HTTP/1.1 200 OK application/pdf 1838195
26/10-16 HTTP/1.1 200 OK application/pdf 1838195
27/10-16 HTTP/1.1 200 OK application/pdf 1838195
27/10-16 HTTP/1.1 200 OK application/pdf 1838195
27/10-16 HTTP/1.1 200 OK application/pdf 1838195
28/10-16 HTTP/1.1 200 OK application/pdf 1838195
28/10-16 HTTP/1.1 200 OK application/pdf 1838195
29/10-16 HTTP/1.1 200 OK application/pdf 1838195
29/10-16 HTTP/1.1 200 OK application/pdf 1838195
30/10-16 HTTP/1.1 200 OK application/pdf 1838195
30/10-16 HTTP/1.1 200 OK application/pdf 1838195
30/10-16 HTTP/1.1 200 OK application/pdf 1838195
31/10-16 N/A 0
01/11-16 HTTP/1.1 200 OK application/pdf 1838195
01/11-16 HTTP/1.1 200 OK application/pdf 1838195
01/11-16 HTTP/1.1 200 OK application/pdf 1838195
02/11-16 HTTP/1.1 200 OK application/pdf 1838195
02/11-16 HTTP/1.1 200 OK application/pdf 1838195
03/11-16 HTTP/1.1 200 OK application/pdf 1838195
03/11-16 HTTP/1.1 200 OK application/pdf 1838195
04/11-16 HTTP/1.1 200 OK application/pdf 1838195
04/11-16 HTTP/1.1 200 OK application/pdf 1838195
05/11-16 HTTP/1.1 200 OK application/pdf 1838195
05/11-16 HTTP/1.1 200 OK application/pdf 1838195
05/11-16 HTTP/1.1 200 OK application/pdf 1838195
06/11-16 HTTP/1.1 200 OK application/pdf 1838195
07/11-16 HTTP/1.1 200 OK application/pdf 1838195
07/11-16 HTTP/1.1 200 OK application/pdf 1838195
08/11-16 HTTP/1.1 200 OK application/pdf 1838195
08/11-16 HTTP/1.1 200 OK application/pdf 1838195
09/11-16 HTTP/1.1 200 OK application/pdf 1838195
09/11-16 HTTP/1.1 200 OK application/pdf 1838195
10/11-16 HTTP/1.1 200 OK application/pdf 1838195
10/11-16 HTTP/1.1 200 OK application/pdf 1838195
11/11-16 HTTP/1.1 200 OK application/pdf 1838195
12/11-16 HTTP/1.1 200 OK application/pdf 1838195
13/11-16 HTTP/1.1 200 OK application/pdf 1838195
14/11-16 HTTP/1.1 200 OK application/pdf 1838195
14/11-16 HTTP/1.1 200 OK application/pdf 1838195
14/11-16 HTTP/1.1 200 OK application/pdf 1838195
15/11-16 HTTP/1.1 200 OK application/pdf 1838195
15/11-16 HTTP/1.1 200 OK application/pdf 1838195
15/11-16 HTTP/1.1 200 OK application/pdf 1838195
16/11-16 HTTP/1.1 200 OK application/pdf 1838195
16/11-16 HTTP/1.1 200 OK application/pdf 1838195
17/11-16 HTTP/1.1 200 OK application/pdf 1838195
18/11-16 HTTP/1.1 200 OK application/pdf 1838195
18/11-16 HTTP/1.1 200 OK application/pdf 1838195
18/11-16 HTTP/1.1 200 OK application/pdf 1838195
19/11-16 HTTP/1.1 200 OK application/pdf 1838195
19/11-16 HTTP/1.1 200 OK application/pdf 1838195
20/11-16 HTTP/1.1 200 OK application/pdf 1838195
20/11-16 HTTP/1.1 200 OK application/pdf 1838195
20/11-16 HTTP/1.1 200 OK application/pdf 1838195
21/11-16 HTTP/1.1 200 OK application/pdf 1838195
21/11-16 HTTP/1.1 200 OK application/pdf 1838195
22/11-16 HTTP/1.1 200 OK application/pdf 1838195
22/11-16 HTTP/1.1 200 OK application/pdf 1838195
23/11-16 HTTP/1.1 200 OK application/pdf 1838195
23/11-16 HTTP/1.1 200 OK application/pdf 1838195
23/11-16 HTTP/1.1 200 OK application/pdf 1838195
23/11-16 HTTP/1.1 200 OK application/pdf 1838195
23/11-16 HTTP/1.1 200 OK application/pdf 1838195
24/11-16 HTTP/1.1 200 OK application/pdf 1838195
24/11-16 HTTP/1.1 200 OK application/pdf 1838195
24/11-16 HTTP/1.1 200 OK application/pdf 1838195
24/11-16 HTTP/1.1 200 OK application/pdf 1838195
24/11-16 HTTP/1.1 200 OK application/pdf 1838195
25/11-16 HTTP/1.1 200 OK application/pdf 1838195
25/11-16 HTTP/1.1 200 OK application/pdf 1838195
25/11-16 HTTP/1.1 200 OK application/pdf 1838195
25/11-16 HTTP/1.1 200 OK application/pdf 1838195
26/11-16 HTTP/1.1 200 OK application/pdf 1838195
26/11-16 HTTP/1.1 200 OK application/pdf 1838195
26/11-16 HTTP/1.1 200 OK application/pdf 1838195
26/11-16 HTTP/1.1 200 OK application/pdf 1838195
26/11-16 HTTP/1.1 200 OK application/pdf 1838195
27/11-16 HTTP/1.1 200 OK application/pdf 1838195
27/11-16 HTTP/1.1 200 OK application/pdf 1838195
27/11-16 HTTP/1.1 200 OK application/pdf 1838195
27/11-16 HTTP/1.1 200 OK application/pdf 1838195
28/11-16 HTTP/1.1 200 OK application/pdf 1838195
28/11-16 HTTP/1.1 200 OK application/pdf 1838195
28/11-16 HTTP/1.1 200 OK application/pdf 1838195
28/11-16 HTTP/1.1 200 OK application/pdf 1838195
29/11-16 HTTP/1.1 200 OK application/pdf 1838195
29/11-16 HTTP/1.1 200 OK application/pdf 1838195
29/11-16 HTTP/1.1 200 OK application/pdf 1838195
29/11-16 HTTP/1.1 200 OK application/pdf 1838195
30/11-16 HTTP/1.1 200 OK application/pdf 1838195
30/11-16 HTTP/1.1 200 OK application/pdf 1838195
30/11-16 HTTP/1.1 200 OK application/pdf 1838195
30/11-16 HTTP/1.1 200 OK application/pdf 1838195
30/11-16 HTTP/1.1 200 OK application/pdf 1838195
01/12-16 HTTP/1.1 200 OK application/pdf 1838195
01/12-16 HTTP/1.1 200 OK application/pdf 1838195
01/12-16 HTTP/1.1 200 OK application/pdf 1838195
01/12-16 HTTP/1.1 200 OK application/pdf 1838195
01/12-16 HTTP/1.1 200 OK application/pdf 1838195
02/12-16 HTTP/1.1 200 OK application/pdf 1838195
02/12-16 HTTP/1.1 200 OK application/pdf 1838195
02/12-16 HTTP/1.1 200 OK application/pdf 1838195
02/12-16 HTTP/1.1 200 OK application/pdf 1838195
03/12-16 HTTP/1.1 200 OK application/pdf 1838195
03/12-16 HTTP/1.1 200 OK application/pdf 1838195
03/12-16 HTTP/1.1 200 OK application/pdf 1838195
03/12-16 HTTP/1.1 200 OK application/pdf 1838195
04/12-16 HTTP/1.1 200 OK application/pdf 1838195
04/12-16 HTTP/1.1 200 OK application/pdf 1838195
04/12-16 HTTP/1.1 200 OK application/pdf 1838195
04/12-16 HTTP/1.1 200 OK application/pdf 1838195
04/12-16 HTTP/1.1 200 OK application/pdf 1838195
05/12-16 HTTP/1.1 200 OK application/pdf 1838195
05/12-16 HTTP/1.1 200 OK application/pdf 1838195
05/12-16 HTTP/1.1 200 OK application/pdf 1838195
05/12-16 HTTP/1.1 200 OK application/pdf 1838195
06/12-16 HTTP/1.1 200 OK application/pdf 1838195
06/12-16 HTTP/1.1 200 OK application/pdf 1838195
06/12-16 HTTP/1.1 200 OK application/pdf 1838195
06/12-16 HTTP/1.1 200 OK application/pdf 1838195
06/12-16 HTTP/1.1 200 OK application/pdf 1838195
07/12-16 HTTP/1.1 200 OK application/pdf 1838195
07/12-16 HTTP/1.1 200 OK application/pdf 1838195
07/12-16 HTTP/1.1 200 OK application/pdf 1838195
07/12-16 HTTP/1.1 200 OK application/pdf 1838195
08/12-16 HTTP/1.1 200 OK application/pdf 1838195
08/12-16 HTTP/1.1 200 OK application/pdf 1838195
08/12-16 HTTP/1.1 200 OK application/pdf 1838195
08/12-16 HTTP/1.1 200 OK application/pdf 1838195
08/12-16 HTTP/1.1 200 OK application/pdf 1838195
09/12-16 HTTP/1.1 200 OK application/pdf 1838195
09/12-16 HTTP/1.1 200 OK application/pdf 1838195
09/12-16 HTTP/1.1 200 OK application/pdf 1838195
09/12-16 HTTP/1.1 200 OK application/pdf 1838195
10/12-16 HTTP/1.1 200 OK application/pdf 1838195
10/12-16 HTTP/1.1 200 OK application/pdf 1838195
10/12-16 HTTP/1.1 200 OK application/pdf 1838195
10/12-16 HTTP/1.1 200 OK application/pdf 1838195
11/12-16 HTTP/1.1 200 OK application/pdf 1838195
11/12-16 HTTP/1.1 200 OK application/pdf 1838195
11/12-16 HTTP/1.1 200 OK application/pdf 1838195
11/12-16 HTTP/1.1 200 OK application/pdf 1838195
11/12-16 HTTP/1.1 200 OK application/pdf 1838195
12/12-16 HTTP/1.1 200 OK application/pdf 1838195
12/12-16 HTTP/1.1 200 OK application/pdf 1838195
12/12-16 HTTP/1.1 200 OK application/pdf 1838195
12/12-16 HTTP/1.1 200 OK application/pdf 1838195
13/12-16 HTTP/1.1 200 OK application/pdf 1838195
13/12-16 HTTP/1.1 200 OK application/pdf 1838195
13/12-16 HTTP/1.1 200 OK application/pdf 1838195
13/12-16 HTTP/1.1 200 OK application/pdf 1838195
14/12-16 HTTP/1.1 200 OK application/pdf 1838195
14/12-16 HTTP/1.1 200 OK application/pdf 1838195
14/12-16 HTTP/1.1 200 OK application/pdf 1838195
14/12-16 HTTP/1.1 200 OK application/pdf 1838195
15/12-16 HTTP/1.1 200 OK application/pdf 1838195
15/12-16 HTTP/1.1 200 OK application/pdf 1838195
15/12-16 HTTP/1.1 200 OK application/pdf 1838195
15/12-16 HTTP/1.1 200 OK application/pdf 1838195
15/12-16 HTTP/1.1 200 OK application/pdf 1838195
16/12-16 HTTP/1.1 200 OK application/pdf 1838195
16/12-16 HTTP/1.1 200 OK application/pdf 1838195
16/12-16 HTTP/1.1 200 OK application/pdf 1838195
16/12-16 HTTP/1.1 200 OK application/pdf 1838195
17/12-16 HTTP/1.1 200 OK application/pdf 1838195
17/12-16 HTTP/1.1 200 OK application/pdf 1838195
17/12-16 HTTP/1.1 200 OK application/pdf 1838195
17/12-16 HTTP/1.1 200 OK application/pdf 1838195
18/12-16 HTTP/1.1 200 OK application/pdf 1838195
18/12-16 HTTP/1.1 200 OK application/pdf 1838195
18/12-16 HTTP/1.1 200 OK application/pdf 1838195
18/12-16 HTTP/1.1 200 OK application/pdf 1838195
19/12-16 HTTP/1.1 200 OK application/pdf 1838195
19/12-16 HTTP/1.1 200 OK application/pdf 1838195
19/12-16 HTTP/1.1 200 OK application/pdf 1838195
19/12-16 HTTP/1.1 200 OK application/pdf 1838195
20/12-16 HTTP/1.1 200 OK application/pdf 1838195
20/12-16 HTTP/1.1 200 OK application/pdf 1838195
20/12-16 HTTP/1.1 200 OK application/pdf 1838195
20/12-16 HTTP/1.1 200 OK application/pdf 1838195
21/12-16 HTTP/1.1 200 OK application/pdf 1838195
21/12-16 HTTP/1.1 200 OK application/pdf 1838195
21/12-16 HTTP/1.1 200 OK application/pdf 1838195
21/12-16 HTTP/1.1 200 OK application/pdf 1838195
22/12-16 HTTP/1.1 200 OK application/pdf 1838195
22/12-16 HTTP/1.1 200 OK application/pdf 1838195
22/12-16 HTTP/1.1 200 OK application/pdf 1838195
22/12-16 HTTP/1.1 200 OK application/pdf 1838195
23/12-16 HTTP/1.1 200 OK application/pdf 1838195
23/12-16 HTTP/1.1 200 OK application/pdf 1838195
23/12-16 HTTP/1.1 200 OK application/pdf 1838195
23/12-16 HTTP/1.1 200 OK application/pdf 1838195
24/12-16 HTTP/1.1 200 OK application/pdf 1838195
24/12-16 HTTP/1.1 200 OK application/pdf 1838195
25/12-16 HTTP/1.1 200 OK application/pdf 1838195
25/12-16 HTTP/1.1 200 OK application/pdf 1838195
25/12-16 HTTP/1.1 200 OK application/pdf 1838195
26/12-16 HTTP/1.1 200 OK application/pdf 1838195
26/12-16 HTTP/1.1 200 OK application/pdf 1838195
26/12-16 HTTP/1.1 200 OK application/pdf 1838195
26/12-16 HTTP/1.1 200 OK application/pdf 1838195
27/12-16 HTTP/1.1 200 OK application/pdf 1838195
27/12-16 HTTP/1.1 200 OK application/pdf 1838195
27/12-16 HTTP/1.1 200 OK application/pdf 1838195
28/12-16 HTTP/1.1 200 OK application/pdf 1838195
28/12-16 HTTP/1.1 200 OK application/pdf 1838195
28/12-16 HTTP/1.1 200 OK application/pdf 1838195
28/12-16 HTTP/1.1 200 OK application/pdf 1838195
29/12-16 HTTP/1.1 200 OK application/pdf 1838195
29/12-16 HTTP/1.1 200 OK application/pdf 1838195
29/12-16 HTTP/1.1 200 OK application/pdf 1838195
29/12-16 HTTP/1.1 200 OK application/pdf 1838195
30/12-16 HTTP/1.1 200 OK application/pdf 1838195
30/12-16 HTTP/1.1 200 OK application/pdf 1838195
30/12-16 HTTP/1.1 200 OK application/pdf 1838195
31/12-16 HTTP/1.1 200 OK application/pdf 1838195
31/12-16 HTTP/1.1 200 OK application/pdf 1838195
31/12-16 HTTP/1.1 200 OK application/pdf 1838195
31/12-16 HTTP/1.1 200 OK application/pdf 1838195
01/01-17 HTTP/1.1 200 OK application/pdf 1838195
01/01-17 HTTP/1.1 200 OK application/pdf 1838195
01/01-17 HTTP/1.1 200 OK application/pdf 1838195
02/01-17 HTTP/1.1 200 OK application/pdf 1838195
02/01-17 HTTP/1.1 200 OK application/pdf 1838195
02/01-17 HTTP/1.1 200 OK application/pdf 1838195
02/01-17 HTTP/1.1 200 OK application/pdf 1838195
03/01-17 HTTP/1.1 200 OK application/pdf 1838195
03/01-17 HTTP/1.1 200 OK application/pdf 1838195
03/01-17 HTTP/1.1 200 OK application/pdf 1838195
04/01-17 HTTP/1.1 200 OK application/pdf 1838195
04/01-17 HTTP/1.1 200 OK application/pdf 1838195
04/01-17 HTTP/1.1 200 OK application/pdf 1838195
04/01-17 HTTP/1.1 200 OK application/pdf 1838195
05/01-17 HTTP/1.1 200 OK application/pdf 1838195
05/01-17 HTTP/1.1 200 OK application/pdf 1838195
05/01-17 HTTP/1.1 200 OK application/pdf 1838195
06/01-17 HTTP/1.1 200 OK application/pdf 1838195
06/01-17 HTTP/1.1 200 OK application/pdf 1838195
06/01-17 HTTP/1.1 200 OK application/pdf 1838195
07/01-17 HTTP/1.1 200 OK application/pdf 1838195
07/01-17 HTTP/1.1 200 OK application/pdf 1838195
07/01-17 HTTP/1.1 200 OK application/pdf 1838195
07/01-17 HTTP/1.1 200 OK application/pdf 1838195
08/01-17 HTTP/1.1 200 OK application/pdf 1838195
08/01-17 HTTP/1.1 200 OK application/pdf 1838195
08/01-17 HTTP/1.1 200 OK application/pdf 1838195
09/01-17 HTTP/1.1 200 OK application/pdf 1838195
09/01-17 HTTP/1.1 200 OK application/pdf 1838195
09/01-17 HTTP/1.1 200 OK application/pdf 1838195
09/01-17 HTTP/1.1 200 OK application/pdf 1838195
09/01-17 HTTP/1.1 200 OK application/pdf 1838195
09/01-17 HTTP/1.1 200 OK application/pdf 1838195
09/01-17 HTTP/1.1 200 OK application/pdf 1838195
09/01-17 HTTP/1.1 200 OK application/pdf 1838195
09/01-17 HTTP/1.1 200 OK application/pdf 1838195
09/01-17 HTTP/1.1 200 OK application/pdf 1838195
09/01-17 HTTP/1.1 200 OK application/pdf 1838195
10/01-17 HTTP/1.1 200 OK application/pdf 1838195
10/01-17 HTTP/1.1 200 OK application/pdf 1838195
10/01-17 HTTP/1.1 200 OK application/pdf 1838195
10/01-17 HTTP/1.1 200 OK application/pdf 1838195
11/01-17 HTTP/1.1 200 OK application/pdf 1838195
11/01-17 HTTP/1.1 200 OK application/pdf 1838195
11/01-17 HTTP/1.1 200 OK application/pdf 1838195
12/01-17 HTTP/1.1 200 OK application/pdf 1838195
12/01-17 HTTP/1.1 200 OK application/pdf 1838195
12/01-17 HTTP/1.1 200 OK application/pdf 1838195
13/01-17 HTTP/1.1 200 OK application/pdf 1838195
13/01-17 HTTP/1.1 200 OK application/pdf 1838195
13/01-17 HTTP/1.1 200 OK application/pdf 1838195
14/01-17 HTTP/1.1 200 OK application/pdf 1838195
14/01-17 HTTP/1.1 200 OK application/pdf 1838195
14/01-17 HTTP/1.1 200 OK application/pdf 1838195
15/01-17 HTTP/1.1 200 OK application/pdf 1838195
15/01-17 HTTP/1.1 200 OK application/pdf 1838195
15/01-17 HTTP/1.1 200 OK application/pdf 1838195
15/01-17 HTTP/1.1 200 OK application/pdf 1838195
16/01-17 HTTP/1.1 200 OK application/pdf 1838195
16/01-17 HTTP/1.1 200 OK application/pdf 1838195
16/01-17 HTTP/1.1 200 OK application/pdf 1838195
17/01-17 HTTP/1.1 200 OK application/pdf 1838195
17/01-17 HTTP/1.1 200 OK application/pdf 1838195
17/01-17 HTTP/1.1 200 OK application/pdf 1838195
18/01-17 HTTP/1.1 200 OK application/pdf 1838195
18/01-17 HTTP/1.1 200 OK application/pdf 1838195
18/01-17 HTTP/1.1 200 OK application/pdf 1838195
19/01-17 HTTP/1.1 200 OK application/pdf 1838195
19/01-17 HTTP/1.1 200 OK application/pdf 1838195
19/01-17 HTTP/1.1 200 OK application/pdf 1838195
20/01-17 HTTP/1.1 200 OK application/pdf 1838195
20/01-17 HTTP/1.1 200 OK application/pdf 1838195
20/01-17 HTTP/1.1 200 OK application/pdf 1838195
21/01-17 HTTP/1.1 200 OK application/pdf 1838195
21/01-17 HTTP/1.1 200 OK application/pdf 1838195
22/01-17 HTTP/1.1 200 OK application/pdf 1838195
22/01-17 HTTP/1.1 200 OK application/pdf 1838195
22/01-17 HTTP/1.1 200 OK application/pdf 1838195
23/01-17 HTTP/1.1 200 OK application/pdf 1838195
23/01-17 HTTP/1.1 200 OK application/pdf 1838195
23/01-17 HTTP/1.1 200 OK application/pdf 1838195
24/01-17 HTTP/1.1 200 OK application/pdf 1838195
24/01-17 HTTP/1.1 200 OK application/pdf 1838195
24/01-17 HTTP/1.1 200 OK application/pdf 1838195
25/01-17 HTTP/1.1 200 OK application/pdf 1838195
25/01-17 HTTP/1.1 200 OK application/pdf 1838195
25/01-17 HTTP/1.1 200 OK application/pdf 1838195
26/01-17 HTTP/1.1 200 OK application/pdf 1838195
26/01-17 HTTP/1.1 200 OK application/pdf 1838195
27/01-17 HTTP/1.1 200 OK application/pdf 1838195
27/01-17 HTTP/1.1 200 OK application/pdf 1838195
27/01-17 HTTP/1.1 200 OK application/pdf 1838195
28/01-17 HTTP/1.1 200 OK application/pdf 1838195
28/01-17 HTTP/1.1 200 OK application/pdf 1838195
29/01-17 HTTP/1.1 200 OK application/pdf 1838195
29/01-17 HTTP/1.1 200 OK application/pdf 1838195
29/01-17 HTTP/1.1 200 OK application/pdf 1838195
30/01-17 HTTP/1.1 200 OK application/pdf 1838195
30/01-17 HTTP/1.1 200 OK application/pdf 1838195
31/01-17 HTTP/1.1 200 OK application/pdf 1838195
31/01-17 HTTP/1.1 200 OK application/pdf 1838195
31/01-17 HTTP/1.1 200 OK application/pdf 1838195
01/02-17 HTTP/1.1 200 OK application/pdf 1838195
01/02-17 HTTP/1.1 200 OK application/pdf 1838195
02/02-17 HTTP/1.1 200 OK application/pdf 1838195
02/02-17 HTTP/1.1 200 OK application/pdf 1838195
02/02-17 HTTP/1.1 200 OK application/pdf 1838195
03/02-17 HTTP/1.1 200 OK application/pdf 1838195
03/02-17 HTTP/1.1 200 OK application/pdf 1838195
04/02-17 HTTP/1.1 200 OK application/pdf 1838195
04/02-17 HTTP/1.1 200 OK application/pdf 1838195
04/02-17 HTTP/1.1 200 OK application/pdf 1838195
05/02-17 HTTP/1.1 200 OK application/pdf 1838195
05/02-17 HTTP/1.1 200 OK application/pdf 1838195
06/02-17 HTTP/1.1 200 OK application/pdf 1838195
06/02-17 HTTP/1.1 200 OK application/pdf 1838195
07/02-17 HTTP/1.1 200 OK application/pdf 1838195
07/02-17 HTTP/1.1 200 OK application/pdf 1838195
07/02-17 HTTP/1.1 200 OK application/pdf 1838195
08/02-17 HTTP/1.1 200 OK application/pdf 1838195
08/02-17 HTTP/1.1 200 OK application/pdf 1838195
09/02-17 HTTP/1.1 200 OK application/pdf 1838195
09/02-17 HTTP/1.1 200 OK application/pdf 1838195
10/02-17 HTTP/1.1 200 OK application/pdf 1838195
10/02-17 HTTP/1.1 200 OK application/pdf 1838195
10/02-17 HTTP/1.1 200 OK application/pdf 1838195
11/02-17 HTTP/1.1 200 OK application/pdf 1838195
11/02-17 HTTP/1.1 200 OK application/pdf 1838195
12/02-17 HTTP/1.1 200 OK application/pdf 1838195
12/02-17 HTTP/1.1 200 OK application/pdf 1838195
13/02-17 HTTP/1.1 200 OK application/pdf 1838195
13/02-17 HTTP/1.1 200 OK application/pdf 1838195
14/02-17 HTTP/1.1 200 OK application/pdf 1838195
14/02-17 HTTP/1.1 200 OK application/pdf 1838195
14/02-17 HTTP/1.1 200 OK application/pdf 1838195
15/02-17 HTTP/1.1 200 OK application/pdf 1838195
15/02-17 HTTP/1.1 200 OK application/pdf 1838195
16/02-17 HTTP/1.1 200 OK application/pdf 1838195
16/02-17 HTTP/1.1 200 OK application/pdf 1838195
17/02-17 HTTP/1.1 200 OK application/pdf 1838195
17/02-17 HTTP/1.1 200 OK application/pdf 1838195
18/02-17 HTTP/1.1 200 OK application/pdf 1838195
18/02-17 HTTP/1.1 200 OK application/pdf 1838195
19/02-17 HTTP/1.1 200 OK application/pdf 1838195
19/02-17 HTTP/1.1 200 OK application/pdf 1838195
20/02-17 HTTP/1.1 200 OK application/pdf 1838195
20/02-17 HTTP/1.1 200 OK application/pdf 1838195
21/02-17 HTTP/1.1 200 OK application/pdf 1838195
21/02-17 HTTP/1.1 200 OK application/pdf 1838195
22/02-17 HTTP/1.1 200 OK application/pdf 1838195
22/02-17 HTTP/1.1 200 OK application/pdf 1838195
22/02-17 HTTP/1.1 200 OK application/pdf 1838195
23/02-17 HTTP/1.1 200 OK application/pdf 1838195
23/02-17 HTTP/1.1 200 OK application/pdf 1838195
24/02-17 HTTP/1.1 200 OK application/pdf 1838195
24/02-17 HTTP/1.1 200 OK application/pdf 1838195
25/02-17 HTTP/1.1 200 OK application/pdf 1838195
25/02-17 HTTP/1.1 200 OK application/pdf 1838195
26/02-17 HTTP/1.1 200 OK application/pdf 1838195
26/02-17 HTTP/1.1 200 OK application/pdf 1838195
27/02-17 HTTP/1.1 200 OK application/pdf 1838195
27/02-17 HTTP/1.1 200 OK application/pdf 1838195
28/02-17 HTTP/1.1 200 OK application/pdf 1838195
01/03-17 HTTP/1.1 200 OK application/pdf 1838195
01/03-17 HTTP/1.1 200 OK application/pdf 1838195
02/03-17 HTTP/1.1 200 OK application/pdf 1838195
02/03-17 HTTP/1.1 200 OK application/pdf 1838195
03/03-17 HTTP/1.1 200 OK application/pdf 1838195
03/03-17 HTTP/1.1 200 OK application/pdf 1838195
04/03-17 HTTP/1.1 200 OK application/pdf 1838195
04/03-17 HTTP/1.1 200 OK application/pdf 1838195
05/03-17 HTTP/1.1 200 OK application/pdf 1838195
06/03-17 HTTP/1.1 200 OK application/pdf 1838195
06/03-17 HTTP/1.1 200 OK application/pdf 1838195
07/03-17 HTTP/1.1 200 OK application/pdf 1838195
09/03-17 HTTP/1.1 200 OK application/pdf 1838195
10/03-17 HTTP/1.1 200 OK application/pdf 1838195
11/03-17 HTTP/1.1 200 OK application/pdf 1838195
12/03-17 HTTP/1.1 200 OK application/pdf 1838195
14/03-17 HTTP/1.1 200 OK application/pdf 1838195
15/03-17 HTTP/1.1 200 OK application/pdf 1838195
16/03-17 HTTP/1.1 200 OK application/pdf 1838195
17/03-17 HTTP/1.1 200 OK application/pdf 1838195
18/03-17 HTTP/1.1 200 OK application/pdf 1838195
19/03-17 HTTP/1.1 200 OK application/pdf 1838195
21/03-17 HTTP/1.1 200 OK application/pdf 1838195
22/03-17 HTTP/1.1 200 OK application/pdf 1838195
23/03-17 HTTP/1.1 200 OK application/pdf 1838195
24/03-17 HTTP/1.1 200 OK application/pdf 1838195
25/03-17 HTTP/1.1 200 OK application/pdf 1838195
27/03-17 HTTP/1.1 200 OK application/pdf 1838195
28/03-17 HTTP/1.1 200 OK application/pdf 1838195
29/03-17 HTTP/1.1 200 OK application/pdf 1838195
30/03-17 HTTP/1.1 200 OK application/pdf 1838195
01/04-17 HTTP/1.1 200 OK application/pdf 1838195
02/04-17 HTTP/1.1 200 OK application/pdf 1838195
03/04-17 HTTP/1.1 200 OK application/pdf 1838195
04/04-17 HTTP/1.1 200 OK application/pdf 1838195
06/04-17 HTTP/1.1 200 OK application/pdf 1838195
07/04-17 HTTP/1.1 200 OK application/pdf 1838195
09/04-17 HTTP/1.1 200 OK application/pdf 1838195
10/04-17 HTTP/1.1 200 OK application/pdf 1838195
11/04-17 HTTP/1.1 200 OK application/pdf 1838195
12/04-17 HTTP/1.1 200 OK application/pdf 1838195
14/04-17 HTTP/1.1 200 OK application/pdf 1838195
15/04-17 HTTP/1.1 200 OK application/pdf 1838195
16/04-17 HTTP/1.1 200 OK application/pdf 1838195
18/04-17 HTTP/1.1 200 OK application/pdf 1838195
19/04-17 HTTP/1.1 200 OK application/pdf 1838195
20/04-17 HTTP/1.1 200 OK application/pdf 1838195
22/04-17 HTTP/1.1 200 OK application/pdf 1838195
23/04-17 HTTP/1.1 200 OK application/pdf 1838195
24/04-17 HTTP/1.1 200 OK application/pdf 1838195
26/04-17 HTTP/1.1 200 OK application/pdf 1838195
27/04-17 HTTP/1.1 200 OK application/pdf 1838195
28/04-17 HTTP/1.1 200 OK application/pdf 1838195
30/04-17 HTTP/1.1 200 OK application/pdf 1838195
01/05-17 HTTP/1.1 200 OK application/pdf 1838195
03/05-17 HTTP/1.1 200 OK application/pdf 1838195
04/05-17 HTTP/1.1 200 OK application/pdf 1838195
05/05-17 HTTP/1.1 200 OK application/pdf 1838195
07/05-17 HTTP/1.1 200 OK application/pdf 1838195
08/05-17 HTTP/1.1 200 OK application/pdf 1838195
10/05-17 HTTP/1.1 200 OK application/pdf 1838195
11/05-17 HTTP/1.1 200 OK application/pdf 1838195
13/05-17 HTTP/1.1 200 OK application/pdf 1838195
14/05-17 HTTP/1.1 200 OK application/pdf 1838195
16/05-17 HTTP/1.1 200 OK application/pdf 1838195
17/05-17 HTTP/1.1 200 OK application/pdf 1838195
19/05-17 HTTP/1.1 200 OK application/pdf 1838195
20/05-17 HTTP/1.1 200 OK application/pdf 1838195
22/05-17 HTTP/1.1 200 OK application/pdf 1838195
24/05-17 HTTP/1.1 200 OK application/pdf 1838195
25/05-17 HTTP/1.1 200 OK application/pdf 1838195
27/05-17 HTTP/1.1 200 OK application/pdf 1838195
29/05-17 HTTP/1.1 200 OK application/pdf 1838195
30/05-17 HTTP/1.1 200 OK application/pdf 1838195
01/06-17 HTTP/1.1 200 OK application/pdf 1838195
03/06-17 HTTP/1.1 200 OK application/pdf 1838195
05/06-17 HTTP/1.1 200 OK application/pdf 1838195
06/06-17 HTTP/1.1 200 OK application/pdf 1838195