Martin Højriis Kristensens hjemmeside

Link Status

Linkhttp://gis.aarhus.dk/lokalplaner/pdf/Aarhus/Pdf/LOKPLAN.150/758!.pdf
Oprettet2007-08-29 02: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/20070829/http://gis.aarhus.dk/lokalplaner/pdf/Aarhus/Pdf/LOKPLAN.150/758!.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 2268191
05/10-15 HTTP/1.1 200 OK application/pdf 2268191
07/10-15 HTTP/1.1 200 OK application/pdf 2268191
08/10-15 HTTP/1.1 200 OK application/pdf 2268191
10/10-15 HTTP/1.1 200 OK application/pdf 2268191
11/10-15 HTTP/1.1 200 OK application/pdf 2268191
13/10-15 HTTP/1.1 200 OK application/pdf 2268191
14/10-15 HTTP/1.1 200 OK application/pdf 2268191
16/10-15 HTTP/1.1 200 OK application/pdf 2268191
17/10-15 HTTP/1.1 200 OK application/pdf 2268191
19/10-15 HTTP/1.1 200 OK application/pdf 2268191
21/10-15 HTTP/1.1 200 OK application/pdf 2268191
22/10-15 HTTP/1.1 200 OK application/pdf 2268191
24/10-15 HTTP/1.1 200 OK application/pdf 2268191
26/10-15 HTTP/1.1 200 OK application/pdf 2268191
28/10-15 HTTP/1.1 200 OK application/pdf 2268191
30/10-15 HTTP/1.1 200 OK application/pdf 2268191
31/10-15 HTTP/1.1 200 OK application/pdf 2268191
02/11-15 HTTP/1.1 200 OK application/pdf 2268191
04/11-15 HTTP/1.1 200 OK application/pdf 2268191
07/11-15 HTTP/1.1 200 OK application/pdf 2268191
08/11-15 HTTP/1.1 200 OK application/pdf 2268191
10/11-15 HTTP/1.1 200 OK application/pdf 2268191
12/11-15 HTTP/1.1 200 OK application/pdf 2268191
14/11-15 HTTP/1.1 200 OK application/pdf 2268191
16/11-15 HTTP/1.1 200 OK application/pdf 2268191
18/11-15 HTTP/1.1 200 OK application/pdf 2268191
20/11-15 HTTP/1.1 200 OK application/pdf 2268191
22/11-15 HTTP/1.1 200 OK application/pdf 2268191
24/11-15 HTTP/1.1 200 OK application/pdf 2268191
26/11-15 HTTP/1.1 200 OK application/pdf 2268191
28/11-15 HTTP/1.1 200 OK application/pdf 2268191
30/11-15 HTTP/1.1 200 OK application/pdf 2268191
02/12-15 HTTP/1.1 200 OK application/pdf 2268191
04/12-15 HTTP/1.1 200 OK application/pdf 2268191
06/12-15 HTTP/1.1 200 OK application/pdf 2268191
08/12-15 HTTP/1.1 200 OK application/pdf 2268191
10/12-15 HTTP/1.1 200 OK application/pdf 2268191
12/12-15 HTTP/1.1 200 OK application/pdf 2268191
14/12-15 HTTP/1.1 200 OK application/pdf 2268191
16/12-15 HTTP/1.1 200 OK application/pdf 2268191
18/12-15 HTTP/1.1 200 OK application/pdf 2268191
20/12-15 HTTP/1.1 200 OK application/pdf 2268191
22/12-15 HTTP/1.1 200 OK application/pdf 2268191
24/12-15 HTTP/1.1 200 OK application/pdf 2268191
26/12-15 HTTP/1.1 200 OK application/pdf 2268191
28/12-15 HTTP/1.1 200 OK application/pdf 2268191
30/12-15 HTTP/1.1 200 OK application/pdf 2268191
01/01-16 HTTP/1.1 200 OK application/pdf 2268191
03/01-16 HTTP/1.1 200 OK application/pdf 2268191
04/01-16 HTTP/1.1 200 OK application/pdf 2268191
06/01-16 HTTP/1.1 200 OK application/pdf 2268191
08/01-16 HTTP/1.1 200 OK application/pdf 2268191
10/01-16 HTTP/1.1 200 OK application/pdf 2268191
12/01-16 HTTP/1.1 200 OK application/pdf 2268191
14/01-16 HTTP/1.1 200 OK application/pdf 2268191
16/01-16 HTTP/1.1 200 OK application/pdf 2268191
18/01-16 HTTP/1.1 200 OK application/pdf 2268191
20/01-16 HTTP/1.1 200 OK application/pdf 2268191
22/01-16 HTTP/1.1 200 OK application/pdf 2268191
24/01-16 HTTP/1.1 200 OK application/pdf 2268191
26/01-16 HTTP/1.1 200 OK application/pdf 2268191
28/01-16 HTTP/1.1 200 OK application/pdf 2268191
29/01-16 HTTP/1.1 200 OK application/pdf 2268191
31/01-16 HTTP/1.1 200 OK application/pdf 2268191
01/02-16 HTTP/1.1 200 OK application/pdf 2268191
03/02-16 HTTP/1.1 200 OK application/pdf 2268191
04/02-16 HTTP/1.1 200 OK application/pdf 2268191
06/02-16 HTTP/1.1 200 OK application/pdf 2268191
07/02-16 HTTP/1.1 200 OK application/pdf 2268191
09/02-16 HTTP/1.1 200 OK application/pdf 2268191
10/02-16 HTTP/1.1 200 OK application/pdf 2268191
12/02-16 HTTP/1.1 200 OK application/pdf 2268191
13/02-16 N/A 0
14/02-16 HTTP/1.1 200 OK application/pdf 2268191
16/02-16 HTTP/1.1 200 OK application/pdf 2268191
17/02-16 HTTP/1.1 200 OK application/pdf 2268191
19/02-16 HTTP/1.1 200 OK application/pdf 2268191
20/02-16 HTTP/1.1 200 OK application/pdf 2268191
22/02-16 HTTP/1.1 200 OK application/pdf 2268191
23/02-16 HTTP/1.1 200 OK application/pdf 2268191
25/02-16 HTTP/1.1 200 OK application/pdf 2268191
26/02-16 HTTP/1.1 200 OK application/pdf 2268191
28/02-16 HTTP/1.1 200 OK application/pdf 2268191
29/02-16 HTTP/1.1 200 OK application/pdf 2268191
02/03-16 HTTP/1.1 200 OK application/pdf 2268191
03/03-16 HTTP/1.1 200 OK application/pdf 2268191
05/03-16 HTTP/1.1 200 OK application/pdf 2268191
06/03-16 HTTP/1.1 200 OK application/pdf 2268191
07/03-16 HTTP/1.1 200 OK application/pdf 2268191
09/03-16 HTTP/1.1 200 OK application/pdf 2268191
10/03-16 HTTP/1.1 200 OK application/pdf 2268191
12/03-16 HTTP/1.1 200 OK application/pdf 2268191
13/03-16 HTTP/1.1 200 OK application/pdf 2268191
15/03-16 HTTP/1.1 200 OK application/pdf 2268191
16/03-16 HTTP/1.1 200 OK application/pdf 2268191
18/03-16 HTTP/1.1 200 OK application/pdf 2268191
19/03-16 HTTP/1.1 200 OK application/pdf 2268191
21/03-16 HTTP/1.1 200 OK application/pdf 2268191
22/03-16 HTTP/1.1 200 OK application/pdf 2268191
24/03-16 HTTP/1.1 200 OK application/pdf 2268191
25/03-16 HTTP/1.1 200 OK application/pdf 2268191
27/03-16 HTTP/1.1 200 OK application/pdf 2268191
28/03-16 HTTP/1.1 200 OK application/pdf 2268191
30/03-16 HTTP/1.1 200 OK application/pdf 2268191
31/03-16 HTTP/1.1 200 OK application/pdf 2268191
02/04-16 HTTP/1.1 200 OK application/pdf 2268191
03/04-16 HTTP/1.1 200 OK application/pdf 2268191
05/04-16 HTTP/1.1 200 OK application/pdf 2268191
06/04-16 HTTP/1.1 200 OK application/pdf 2268191
06/04-16 HTTP/1.1 200 OK application/pdf 2268191
07/04-16 HTTP/1.1 200 OK application/pdf 2268191
08/04-16 HTTP/1.1 200 OK application/pdf 2268191
09/04-16 HTTP/1.1 200 OK application/pdf 2268191
09/04-16 HTTP/1.1 200 OK application/pdf 2268191
10/04-16 HTTP/1.1 200 OK application/pdf 2268191
11/04-16 HTTP/1.1 200 OK application/pdf 2268191
12/04-16 HTTP/1.1 200 OK application/pdf 2268191
12/04-16 HTTP/1.1 200 OK application/pdf 2268191
13/04-16 HTTP/1.1 200 OK application/pdf 2268191
14/04-16 HTTP/1.1 200 OK application/pdf 2268191
15/04-16 HTTP/1.1 200 OK application/pdf 2268191
16/04-16 HTTP/1.1 200 OK application/pdf 2268191
17/04-16 HTTP/1.1 200 OK application/pdf 2268191
18/04-16 HTTP/1.1 200 OK application/pdf 2268191
18/04-16 HTTP/1.1 200 OK application/pdf 2268191
19/04-16 HTTP/1.1 200 OK application/pdf 2268191
19/04-16 HTTP/1.1 200 OK application/pdf 2268191
19/04-16 HTTP/1.1 200 OK application/pdf 2268191
20/04-16 HTTP/1.1 200 OK application/pdf 2268191
20/04-16 HTTP/1.1 200 OK application/pdf 2268191
20/04-16 HTTP/1.1 200 OK application/pdf 2268191
20/04-16 HTTP/1.1 200 OK application/pdf 2268191
20/04-16 HTTP/1.1 200 OK application/pdf 2268191
20/04-16 HTTP/1.1 200 OK application/pdf 2268191
21/04-16 HTTP/1.1 200 OK application/pdf 2268191
21/04-16 HTTP/1.1 200 OK application/pdf 2268191
21/04-16 HTTP/1.1 200 OK application/pdf 2268191
21/04-16 HTTP/1.1 200 OK application/pdf 2268191
21/04-16 HTTP/1.1 200 OK application/pdf 2268191
21/04-16 HTTP/1.1 200 OK application/pdf 2268191
22/04-16 HTTP/1.1 200 OK application/pdf 2268191
22/04-16 HTTP/1.1 200 OK application/pdf 2268191
22/04-16 HTTP/1.1 200 OK application/pdf 2268191
22/04-16 HTTP/1.1 200 OK application/pdf 2268191
22/04-16 HTTP/1.1 200 OK application/pdf 2268191
23/04-16 HTTP/1.1 200 OK application/pdf 2268191
23/04-16 HTTP/1.1 200 OK application/pdf 2268191
23/04-16 HTTP/1.1 200 OK application/pdf 2268191
23/04-16 HTTP/1.1 200 OK application/pdf 2268191
23/04-16 HTTP/1.1 200 OK application/pdf 2268191
24/04-16 HTTP/1.1 200 OK application/pdf 2268191
24/04-16 HTTP/1.1 200 OK application/pdf 2268191
24/04-16 HTTP/1.1 200 OK application/pdf 2268191
24/04-16 HTTP/1.1 200 OK application/pdf 2268191
24/04-16 HTTP/1.1 200 OK application/pdf 2268191
24/04-16 HTTP/1.1 200 OK application/pdf 2268191
25/04-16 HTTP/1.1 200 OK application/pdf 2268191
25/04-16 HTTP/1.1 200 OK application/pdf 2268191
25/04-16 HTTP/1.1 200 OK application/pdf 2268191
25/04-16 HTTP/1.1 200 OK application/pdf 2268191
25/04-16 HTTP/1.1 200 OK application/pdf 2268191
26/04-16 HTTP/1.1 200 OK application/pdf 2268191
26/04-16 HTTP/1.1 200 OK application/pdf 2268191
26/04-16 HTTP/1.1 200 OK application/pdf 2268191
26/04-16 HTTP/1.1 200 OK application/pdf 2268191
26/04-16 HTTP/1.1 200 OK application/pdf 2268191
26/04-16 HTTP/1.1 200 OK application/pdf 2268191
27/04-16 HTTP/1.1 200 OK application/pdf 2268191
27/04-16 HTTP/1.1 200 OK application/pdf 2268191
27/04-16 HTTP/1.1 200 OK application/pdf 2268191
27/04-16 HTTP/1.1 200 OK application/pdf 2268191
27/04-16 HTTP/1.1 200 OK application/pdf 2268191
28/04-16 HTTP/1.1 200 OK application/pdf 2268191
28/04-16 HTTP/1.1 200 OK application/pdf 2268191
28/04-16 HTTP/1.1 200 OK application/pdf 2268191
28/04-16 HTTP/1.1 200 OK application/pdf 2268191
28/04-16 HTTP/1.1 200 OK application/pdf 2268191
28/04-16 HTTP/1.1 200 OK application/pdf 2268191
29/04-16 HTTP/1.1 200 OK application/pdf 2268191
29/04-16 HTTP/1.1 200 OK application/pdf 2268191
29/04-16 HTTP/1.1 200 OK application/pdf 2268191
29/04-16 HTTP/1.1 200 OK application/pdf 2268191
29/04-16 HTTP/1.1 200 OK application/pdf 2268191
30/04-16 HTTP/1.1 200 OK application/pdf 2268191
30/04-16 HTTP/1.1 200 OK application/pdf 2268191
30/04-16 HTTP/1.1 200 OK application/pdf 2268191
30/04-16 HTTP/1.1 200 OK application/pdf 2268191
30/04-16 HTTP/1.1 200 OK application/pdf 2268191
30/04-16 HTTP/1.1 200 OK application/pdf 2268191
01/05-16 HTTP/1.1 200 OK application/pdf 2268191
01/05-16 HTTP/1.1 200 OK application/pdf 2268191
01/05-16 HTTP/1.1 200 OK application/pdf 2268191
01/05-16 HTTP/1.1 200 OK application/pdf 2268191
01/05-16 HTTP/1.1 200 OK application/pdf 2268191
02/05-16 HTTP/1.1 200 OK application/pdf 2268191
02/05-16 HTTP/1.1 200 OK application/pdf 2268191
02/05-16 HTTP/1.1 200 OK application/pdf 2268191
02/05-16 HTTP/1.1 200 OK application/pdf 2268191
02/05-16 HTTP/1.1 200 OK application/pdf 2268191
02/05-16 HTTP/1.1 200 OK application/pdf 2268191
03/05-16 HTTP/1.1 200 OK application/pdf 2268191
03/05-16 HTTP/1.1 200 OK application/pdf 2268191
03/05-16 HTTP/1.1 200 OK application/pdf 2268191
03/05-16 HTTP/1.1 200 OK application/pdf 2268191
03/05-16 HTTP/1.1 200 OK application/pdf 2268191
04/05-16 HTTP/1.1 200 OK application/pdf 2268191
04/05-16 HTTP/1.1 200 OK application/pdf 2268191
04/05-16 HTTP/1.1 200 OK application/pdf 2268191
04/05-16 HTTP/1.1 200 OK application/pdf 2268191
04/05-16 HTTP/1.1 200 OK application/pdf 2268191
04/05-16 HTTP/1.1 200 OK application/pdf 2268191
05/05-16 HTTP/1.1 200 OK application/pdf 2268191
05/05-16 HTTP/1.1 200 OK application/pdf 2268191
05/05-16 HTTP/1.1 200 OK application/pdf 2268191
05/05-16 HTTP/1.1 200 OK application/pdf 2268191
05/05-16 HTTP/1.1 200 OK application/pdf 2268191
06/05-16 HTTP/1.1 200 OK application/pdf 2268191
06/05-16 HTTP/1.1 200 OK application/pdf 2268191
06/05-16 HTTP/1.1 200 OK application/pdf 2268191
06/05-16 HTTP/1.1 200 OK application/pdf 2268191
06/05-16 HTTP/1.1 200 OK application/pdf 2268191
07/05-16 HTTP/1.1 200 OK application/pdf 2268191
07/05-16 HTTP/1.1 200 OK application/pdf 2268191
07/05-16 HTTP/1.1 200 OK application/pdf 2268191
07/05-16 HTTP/1.1 200 OK application/pdf 2268191
07/05-16 HTTP/1.1 200 OK application/pdf 2268191
08/05-16 HTTP/1.1 200 OK application/pdf 2268191
08/05-16 HTTP/1.1 200 OK application/pdf 2268191
08/05-16 HTTP/1.1 200 OK application/pdf 2268191
08/05-16 HTTP/1.1 200 OK application/pdf 2268191
08/05-16 HTTP/1.1 200 OK application/pdf 2268191
08/05-16 HTTP/1.1 200 OK application/pdf 2268191
09/05-16 HTTP/1.1 200 OK application/pdf 2268191
09/05-16 HTTP/1.1 200 OK application/pdf 2268191
09/05-16 HTTP/1.1 200 OK application/pdf 2268191
09/05-16 HTTP/1.1 200 OK application/pdf 2268191
09/05-16 HTTP/1.1 200 OK application/pdf 2268191
10/05-16 HTTP/1.1 200 OK application/pdf 2268191
10/05-16 HTTP/1.1 200 OK application/pdf 2268191
10/05-16 HTTP/1.1 200 OK application/pdf 2268191
10/05-16 HTTP/1.1 200 OK application/pdf 2268191
10/05-16 HTTP/1.1 200 OK application/pdf 2268191
10/05-16 HTTP/1.1 200 OK application/pdf 2268191
11/05-16 HTTP/1.1 200 OK application/pdf 2268191
11/05-16 HTTP/1.1 200 OK application/pdf 2268191
11/05-16 HTTP/1.1 200 OK application/pdf 2268191
11/05-16 HTTP/1.1 200 OK application/pdf 2268191
11/05-16 HTTP/1.1 200 OK application/pdf 2268191
12/05-16 HTTP/1.1 200 OK application/pdf 2268191
12/05-16 HTTP/1.1 200 OK application/pdf 2268191
12/05-16 HTTP/1.1 200 OK application/pdf 2268191
12/05-16 HTTP/1.1 200 OK application/pdf 2268191
12/05-16 HTTP/1.1 200 OK application/pdf 2268191
12/05-16 HTTP/1.1 200 OK application/pdf 2268191
13/05-16 HTTP/1.1 200 OK application/pdf 2268191
13/05-16 HTTP/1.1 200 OK application/pdf 2268191
13/05-16 HTTP/1.1 200 OK application/pdf 2268191
13/05-16 HTTP/1.1 200 OK application/pdf 2268191
13/05-16 HTTP/1.1 200 OK application/pdf 2268191
14/05-16 HTTP/1.1 200 OK application/pdf 2268191
14/05-16 HTTP/1.1 200 OK application/pdf 2268191
14/05-16 HTTP/1.1 200 OK application/pdf 2268191
14/05-16 HTTP/1.1 200 OK application/pdf 2268191
14/05-16 HTTP/1.1 200 OK application/pdf 2268191
15/05-16 HTTP/1.1 200 OK application/pdf 2268191
15/05-16 HTTP/1.1 200 OK application/pdf 2268191
15/05-16 HTTP/1.1 200 OK application/pdf 2268191
15/05-16 HTTP/1.1 200 OK application/pdf 2268191
15/05-16 HTTP/1.1 200 OK application/pdf 2268191
15/05-16 HTTP/1.1 200 OK application/pdf 2268191
16/05-16 HTTP/1.1 200 OK application/pdf 2268191
16/05-16 HTTP/1.1 200 OK application/pdf 2268191
16/05-16 HTTP/1.1 200 OK application/pdf 2268191
16/05-16 HTTP/1.1 200 OK application/pdf 2268191
16/05-16 HTTP/1.1 200 OK application/pdf 2268191
17/05-16 HTTP/1.1 200 OK application/pdf 2268191
17/05-16 HTTP/1.1 200 OK application/pdf 2268191
17/05-16 HTTP/1.1 200 OK application/pdf 2268191
17/05-16 HTTP/1.1 200 OK application/pdf 2268191
17/05-16 HTTP/1.1 200 OK application/pdf 2268191
17/05-16 HTTP/1.1 200 OK application/pdf 2268191
18/05-16 HTTP/1.1 200 OK application/pdf 2268191
18/05-16 HTTP/1.1 200 OK application/pdf 2268191
18/05-16 HTTP/1.1 200 OK application/pdf 2268191
18/05-16 HTTP/1.1 200 OK application/pdf 2268191
18/05-16 HTTP/1.1 200 OK application/pdf 2268191
19/05-16 HTTP/1.1 200 OK application/pdf 2268191
19/05-16 HTTP/1.1 200 OK application/pdf 2268191
19/05-16 HTTP/1.1 200 OK application/pdf 2268191
19/05-16 HTTP/1.1 200 OK application/pdf 2268191
19/05-16 HTTP/1.1 200 OK application/pdf 2268191
20/05-16 HTTP/1.1 200 OK application/pdf 2268191
20/05-16 HTTP/1.1 200 OK application/pdf 2268191
20/05-16 HTTP/1.1 200 OK application/pdf 2268191
20/05-16 HTTP/1.1 200 OK application/pdf 2268191
20/05-16 HTTP/1.1 200 OK application/pdf 2268191
20/05-16 HTTP/1.1 200 OK application/pdf 2268191
21/05-16 HTTP/1.1 200 OK application/pdf 2268191
21/05-16 HTTP/1.1 200 OK application/pdf 2268191
21/05-16 HTTP/1.1 200 OK application/pdf 2268191
21/05-16 HTTP/1.1 200 OK application/pdf 2268191
21/05-16 HTTP/1.1 200 OK application/pdf 2268191
22/05-16 HTTP/1.1 200 OK application/pdf 2268191
22/05-16 HTTP/1.1 200 OK application/pdf 2268191
22/05-16 HTTP/1.1 200 OK application/pdf 2268191
22/05-16 HTTP/1.1 200 OK application/pdf 2268191
22/05-16 HTTP/1.1 200 OK application/pdf 2268191
22/05-16 HTTP/1.1 200 OK application/pdf 2268191
23/05-16 HTTP/1.1 200 OK application/pdf 2268191
23/05-16 HTTP/1.1 200 OK application/pdf 2268191
23/05-16 HTTP/1.1 200 OK application/pdf 2268191
23/05-16 HTTP/1.1 200 OK application/pdf 2268191
23/05-16 HTTP/1.1 200 OK application/pdf 2268191
24/05-16 HTTP/1.1 200 OK application/pdf 2268191
24/05-16 HTTP/1.1 200 OK application/pdf 2268191
24/05-16 HTTP/1.1 200 OK application/pdf 2268191
24/05-16 HTTP/1.1 200 OK application/pdf 2268191
24/05-16 HTTP/1.1 200 OK application/pdf 2268191
25/05-16 HTTP/1.1 200 OK application/pdf 2268191
25/05-16 HTTP/1.1 200 OK application/pdf 2268191
25/05-16 HTTP/1.1 200 OK application/pdf 2268191
25/05-16 HTTP/1.1 200 OK application/pdf 2268191
25/05-16 HTTP/1.1 200 OK application/pdf 2268191
25/05-16 HTTP/1.1 200 OK application/pdf 2268191
26/05-16 HTTP/1.1 200 OK application/pdf 2268191
26/05-16 HTTP/1.1 200 OK application/pdf 2268191
26/05-16 HTTP/1.1 200 OK application/pdf 2268191
26/05-16 HTTP/1.1 200 OK application/pdf 2268191
26/05-16 HTTP/1.1 200 OK application/pdf 2268191
27/05-16 HTTP/1.1 200 OK application/pdf 2268191
27/05-16 HTTP/1.1 200 OK application/pdf 2268191
27/05-16 HTTP/1.1 200 OK application/pdf 2268191
27/05-16 HTTP/1.1 200 OK application/pdf 2268191
27/05-16 HTTP/1.1 200 OK application/pdf 2268191
27/05-16 HTTP/1.1 200 OK application/pdf 2268191
28/05-16 HTTP/1.1 200 OK application/pdf 2268191
28/05-16 HTTP/1.1 200 OK application/pdf 2268191
28/05-16 HTTP/1.1 200 OK application/pdf 2268191
28/05-16 HTTP/1.1 200 OK application/pdf 2268191
28/05-16 HTTP/1.1 200 OK application/pdf 2268191
29/05-16 HTTP/1.1 200 OK application/pdf 2268191
29/05-16 HTTP/1.1 200 OK application/pdf 2268191
29/05-16 HTTP/1.1 200 OK application/pdf 2268191
29/05-16 HTTP/1.1 200 OK application/pdf 2268191
29/05-16 HTTP/1.1 200 OK application/pdf 2268191
30/05-16 HTTP/1.1 200 OK application/pdf 2268191
30/05-16 HTTP/1.1 200 OK application/pdf 2268191
30/05-16 HTTP/1.1 200 OK application/pdf 2268191
30/05-16 HTTP/1.1 200 OK application/pdf 2268191
30/05-16 HTTP/1.1 200 OK application/pdf 2268191
31/05-16 HTTP/1.1 200 OK application/pdf 2268191
31/05-16 HTTP/1.1 200 OK application/pdf 2268191
31/05-16 HTTP/1.1 200 OK application/pdf 2268191
31/05-16 HTTP/1.1 200 OK application/pdf 2268191
31/05-16 HTTP/1.1 200 OK application/pdf 2268191
31/05-16 HTTP/1.1 200 OK application/pdf 2268191
01/06-16 HTTP/1.1 200 OK application/pdf 2268191
01/06-16 HTTP/1.1 200 OK application/pdf 2268191
01/06-16 HTTP/1.1 200 OK application/pdf 2268191
01/06-16 HTTP/1.1 200 OK application/pdf 2268191
01/06-16 HTTP/1.1 200 OK application/pdf 2268191
02/06-16 HTTP/1.1 200 OK application/pdf 2268191
02/06-16 HTTP/1.1 200 OK application/pdf 2268191
02/06-16 HTTP/1.1 200 OK application/pdf 2268191
02/06-16 HTTP/1.1 200 OK application/pdf 2268191
02/06-16 HTTP/1.1 200 OK application/pdf 2268191
03/06-16 HTTP/1.1 200 OK application/pdf 2268191
03/06-16 HTTP/1.1 200 OK application/pdf 2268191
03/06-16 HTTP/1.1 200 OK application/pdf 2268191
03/06-16 HTTP/1.1 200 OK application/pdf 2268191
03/06-16 HTTP/1.1 200 OK application/pdf 2268191
03/06-16 HTTP/1.1 200 OK application/pdf 2268191
04/06-16 HTTP/1.1 200 OK application/pdf 2268191
04/06-16 HTTP/1.1 200 OK application/pdf 2268191
04/06-16 HTTP/1.1 200 OK application/pdf 2268191
04/06-16 HTTP/1.1 200 OK application/pdf 2268191
04/06-16 HTTP/1.1 200 OK application/pdf 2268191
05/06-16 HTTP/1.1 200 OK application/pdf 2268191
05/06-16 HTTP/1.1 200 OK application/pdf 2268191
05/06-16 HTTP/1.1 200 OK application/pdf 2268191
05/06-16 HTTP/1.1 200 OK application/pdf 2268191
05/06-16 HTTP/1.1 200 OK application/pdf 2268191
05/06-16 HTTP/1.1 200 OK application/pdf 2268191
06/06-16 HTTP/1.1 200 OK application/pdf 2268191
06/06-16 HTTP/1.1 200 OK application/pdf 2268191
06/06-16 HTTP/1.1 200 OK application/pdf 2268191
06/06-16 HTTP/1.1 200 OK application/pdf 2268191
06/06-16 HTTP/1.1 200 OK application/pdf 2268191
07/06-16 HTTP/1.1 200 OK application/pdf 2268191
07/06-16 HTTP/1.1 200 OK application/pdf 2268191
07/06-16 HTTP/1.1 200 OK application/pdf 2268191
07/06-16 HTTP/1.1 200 OK application/pdf 2268191
07/06-16 HTTP/1.1 200 OK application/pdf 2268191
07/06-16 HTTP/1.1 200 OK application/pdf 2268191
08/06-16 HTTP/1.1 200 OK application/pdf 2268191
08/06-16 HTTP/1.1 200 OK application/pdf 2268191
08/06-16 HTTP/1.1 200 OK application/pdf 2268191
08/06-16 HTTP/1.1 200 OK application/pdf 2268191
08/06-16 HTTP/1.1 200 OK application/pdf 2268191
09/06-16 HTTP/1.1 200 OK application/pdf 2268191
09/06-16 HTTP/1.1 200 OK application/pdf 2268191
09/06-16 HTTP/1.1 200 OK application/pdf 2268191
09/06-16 HTTP/1.1 200 OK application/pdf 2268191
09/06-16 HTTP/1.1 200 OK application/pdf 2268191
10/06-16 HTTP/1.1 200 OK application/pdf 2268191
10/06-16 HTTP/1.1 200 OK application/pdf 2268191
10/06-16 HTTP/1.1 200 OK application/pdf 2268191
10/06-16 HTTP/1.1 200 OK application/pdf 2268191
10/06-16 HTTP/1.1 200 OK application/pdf 2268191
10/06-16 HTTP/1.1 200 OK application/pdf 2268191
11/06-16 HTTP/1.1 200 OK application/pdf 2268191
11/06-16 HTTP/1.1 200 OK application/pdf 2268191
11/06-16 HTTP/1.1 200 OK application/pdf 2268191
11/06-16 HTTP/1.1 200 OK application/pdf 2268191
11/06-16 HTTP/1.1 200 OK application/pdf 2268191
12/06-16 HTTP/1.1 200 OK application/pdf 2268191
12/06-16 HTTP/1.1 200 OK application/pdf 2268191
12/06-16 HTTP/1.1 200 OK application/pdf 2268191
12/06-16 HTTP/1.1 200 OK application/pdf 2268191
12/06-16 HTTP/1.1 200 OK application/pdf 2268191
13/06-16 HTTP/1.1 200 OK application/pdf 2268191
13/06-16 HTTP/1.1 200 OK application/pdf 2268191
13/06-16 HTTP/1.1 200 OK application/pdf 2268191
13/06-16 HTTP/1.1 200 OK application/pdf 2268191
13/06-16 HTTP/1.1 200 OK application/pdf 2268191
13/06-16 HTTP/1.1 200 OK application/pdf 2268191
14/06-16 HTTP/1.1 200 OK application/pdf 2268191
14/06-16 HTTP/1.1 200 OK application/pdf 2268191
14/06-16 HTTP/1.1 200 OK application/pdf 2268191
14/06-16 HTTP/1.1 200 OK application/pdf 2268191
14/06-16 HTTP/1.1 200 OK application/pdf 2268191
15/06-16 HTTP/1.1 200 OK application/pdf 2268191
15/06-16 HTTP/1.1 200 OK application/pdf 2268191
15/06-16 HTTP/1.1 200 OK application/pdf 2268191
15/06-16 HTTP/1.1 200 OK application/pdf 2268191
15/06-16 HTTP/1.1 200 OK application/pdf 2268191
16/06-16 HTTP/1.1 200 OK application/pdf 2268191
16/06-16 HTTP/1.1 200 OK application/pdf 2268191
16/06-16 HTTP/1.1 200 OK application/pdf 2268191
16/06-16 HTTP/1.1 200 OK application/pdf 2268191
16/06-16 HTTP/1.1 200 OK application/pdf 2268191
16/06-16 HTTP/1.1 200 OK application/pdf 2268191
17/06-16 HTTP/1.1 200 OK application/pdf 2268191
17/06-16 HTTP/1.1 200 OK application/pdf 2268191
17/06-16 HTTP/1.1 200 OK application/pdf 2268191
17/06-16 HTTP/1.1 200 OK application/pdf 2268191
17/06-16 HTTP/1.1 200 OK application/pdf 2268191
18/06-16 HTTP/1.1 200 OK application/pdf 2268191
18/06-16 HTTP/1.1 200 OK application/pdf 2268191
18/06-16 HTTP/1.1 200 OK application/pdf 2268191
18/06-16 HTTP/1.1 200 OK application/pdf 2268191
18/06-16 HTTP/1.1 200 OK application/pdf 2268191
19/06-16 HTTP/1.1 200 OK application/pdf 2268191
19/06-16 HTTP/1.1 200 OK application/pdf 2268191
19/06-16 HTTP/1.1 200 OK application/pdf 2268191
19/06-16 HTTP/1.1 200 OK application/pdf 2268191
19/06-16 HTTP/1.1 200 OK application/pdf 2268191
19/06-16 HTTP/1.1 200 OK application/pdf 2268191
20/06-16 HTTP/1.1 200 OK application/pdf 2268191
20/06-16 HTTP/1.1 200 OK application/pdf 2268191
20/06-16 HTTP/1.1 200 OK application/pdf 2268191
20/06-16 HTTP/1.1 200 OK application/pdf 2268191
20/06-16 HTTP/1.1 200 OK application/pdf 2268191
21/06-16 HTTP/1.1 200 OK application/pdf 2268191
21/06-16 HTTP/1.1 200 OK application/pdf 2268191
21/06-16 HTTP/1.1 200 OK application/pdf 2268191
21/06-16 HTTP/1.1 200 OK application/pdf 2268191
21/06-16 HTTP/1.1 200 OK application/pdf 2268191
21/06-16 HTTP/1.1 200 OK application/pdf 2268191
22/06-16 HTTP/1.1 200 OK application/pdf 2268191
22/06-16 HTTP/1.1 200 OK application/pdf 2268191
22/06-16 HTTP/1.1 200 OK application/pdf 2268191
22/06-16 HTTP/1.1 200 OK application/pdf 2268191
22/06-16 HTTP/1.1 200 OK application/pdf 2268191
23/06-16 HTTP/1.1 200 OK application/pdf 2268191
23/06-16 HTTP/1.1 200 OK application/pdf 2268191
23/06-16 HTTP/1.1 200 OK application/pdf 2268191
23/06-16 HTTP/1.1 200 OK application/pdf 2268191
23/06-16 HTTP/1.1 200 OK application/pdf 2268191
24/06-16 HTTP/1.1 200 OK application/pdf 2268191
24/06-16 HTTP/1.1 200 OK application/pdf 2268191
24/06-16 HTTP/1.1 200 OK application/pdf 2268191
24/06-16 HTTP/1.1 200 OK application/pdf 2268191
24/06-16 HTTP/1.1 200 OK application/pdf 2268191
24/06-16 HTTP/1.1 200 OK application/pdf 2268191
25/06-16 HTTP/1.1 200 OK application/pdf 2268191
25/06-16 HTTP/1.1 200 OK application/pdf 2268191
25/06-16 HTTP/1.1 200 OK application/pdf 2268191
25/06-16 HTTP/1.1 200 OK application/pdf 2268191
25/06-16 HTTP/1.1 200 OK application/pdf 2268191
26/06-16 HTTP/1.1 200 OK application/pdf 2268191
26/06-16 HTTP/1.1 200 OK application/pdf 2268191
26/06-16 HTTP/1.1 200 OK application/pdf 2268191
26/06-16 HTTP/1.1 200 OK application/pdf 2268191
26/06-16 HTTP/1.1 200 OK application/pdf 2268191
26/06-16 HTTP/1.1 200 OK application/pdf 2268191
27/06-16 HTTP/1.1 200 OK application/pdf 2268191
27/06-16 HTTP/1.1 200 OK application/pdf 2268191
27/06-16 HTTP/1.1 200 OK application/pdf 2268191
27/06-16 HTTP/1.1 200 OK application/pdf 2268191
27/06-16 HTTP/1.1 200 OK application/pdf 2268191
28/06-16 HTTP/1.1 200 OK application/pdf 2268191
28/06-16 HTTP/1.1 200 OK application/pdf 2268191
28/06-16 HTTP/1.1 200 OK application/pdf 2268191
28/06-16 HTTP/1.1 200 OK application/pdf 2268191
28/06-16 HTTP/1.1 200 OK application/pdf 2268191
29/06-16 HTTP/1.1 200 OK application/pdf 2268191
29/06-16 HTTP/1.1 200 OK application/pdf 2268191
29/06-16 HTTP/1.1 200 OK application/pdf 2268191
29/06-16 HTTP/1.1 200 OK application/pdf 2268191
29/06-16 HTTP/1.1 200 OK application/pdf 2268191
29/06-16 HTTP/1.1 200 OK application/pdf 2268191
30/06-16 HTTP/1.1 200 OK application/pdf 2268191
30/06-16 HTTP/1.1 200 OK application/pdf 2268191
30/06-16 HTTP/1.1 200 OK application/pdf 2268191
30/06-16 HTTP/1.1 200 OK application/pdf 2268191
30/06-16 HTTP/1.1 200 OK application/pdf 2268191
01/07-16 HTTP/1.1 200 OK application/pdf 2268191
01/07-16 HTTP/1.1 200 OK application/pdf 2268191
01/07-16 HTTP/1.1 200 OK application/pdf 2268191
01/07-16 HTTP/1.1 200 OK application/pdf 2268191
01/07-16 HTTP/1.1 200 OK application/pdf 2268191
02/07-16 HTTP/1.1 200 OK application/pdf 2268191
02/07-16 HTTP/1.1 200 OK application/pdf 2268191
02/07-16 HTTP/1.1 200 OK application/pdf 2268191
02/07-16 HTTP/1.1 200 OK application/pdf 2268191
02/07-16 HTTP/1.1 200 OK application/pdf 2268191
02/07-16 HTTP/1.1 200 OK application/pdf 2268191
03/07-16 HTTP/1.1 200 OK application/pdf 2268191
03/07-16 HTTP/1.1 200 OK application/pdf 2268191
03/07-16 HTTP/1.1 200 OK application/pdf 2268191
03/07-16 HTTP/1.1 200 OK application/pdf 2268191
03/07-16 HTTP/1.1 200 OK application/pdf 2268191
04/07-16 HTTP/1.1 200 OK application/pdf 2268191
04/07-16 HTTP/1.1 200 OK application/pdf 2268191
04/07-16 HTTP/1.1 200 OK application/pdf 2268191
04/07-16 HTTP/1.1 200 OK application/pdf 2268191
04/07-16 HTTP/1.1 200 OK application/pdf 2268191
05/07-16 HTTP/1.1 200 OK application/pdf 2268191
05/07-16 HTTP/1.1 200 OK application/pdf 2268191
05/07-16 HTTP/1.1 200 OK application/pdf 2268191
05/07-16 HTTP/1.1 200 OK application/pdf 2268191
05/07-16 HTTP/1.1 200 OK application/pdf 2268191
06/07-16 HTTP/1.1 200 OK application/pdf 2268191
06/07-16 HTTP/1.1 200 OK application/pdf 2268191
06/07-16 HTTP/1.1 200 OK application/pdf 2268191
06/07-16 HTTP/1.1 200 OK application/pdf 2268191
06/07-16 HTTP/1.1 200 OK application/pdf 2268191
06/07-16 HTTP/1.1 200 OK application/pdf 2268191
07/07-16 HTTP/1.1 200 OK application/pdf 2268191
07/07-16 HTTP/1.1 200 OK application/pdf 2268191
07/07-16 HTTP/1.1 200 OK application/pdf 2268191
07/07-16 HTTP/1.1 200 OK application/pdf 2268191
07/07-16 HTTP/1.1 200 OK application/pdf 2268191
08/07-16 HTTP/1.1 200 OK application/pdf 2268191
08/07-16 HTTP/1.1 200 OK application/pdf 2268191
08/07-16 HTTP/1.1 200 OK application/pdf 2268191
08/07-16 HTTP/1.1 200 OK application/pdf 2268191
08/07-16 HTTP/1.1 200 OK application/pdf 2268191
09/07-16 HTTP/1.1 200 OK application/pdf 2268191
09/07-16 HTTP/1.1 200 OK application/pdf 2268191
09/07-16 HTTP/1.1 200 OK application/pdf 2268191
09/07-16 HTTP/1.1 200 OK application/pdf 2268191
09/07-16 HTTP/1.1 200 OK application/pdf 2268191
09/07-16 HTTP/1.1 200 OK application/pdf 2268191
10/07-16 HTTP/1.1 200 OK application/pdf 2268191
10/07-16 HTTP/1.1 200 OK application/pdf 2268191
10/07-16 HTTP/1.1 200 OK application/pdf 2268191
10/07-16 HTTP/1.1 200 OK application/pdf 2268191
10/07-16 HTTP/1.1 200 OK application/pdf 2268191
11/07-16 HTTP/1.1 200 OK application/pdf 2268191
11/07-16 HTTP/1.1 200 OK application/pdf 2268191
11/07-16 HTTP/1.1 200 OK application/pdf 2268191
11/07-16 HTTP/1.1 200 OK application/pdf 2268191
11/07-16 HTTP/1.1 200 OK application/pdf 2268191
12/07-16 HTTP/1.1 200 OK application/pdf 2268191
12/07-16 HTTP/1.1 200 OK application/pdf 2268191
12/07-16 HTTP/1.1 200 OK application/pdf 2268191
12/07-16 HTTP/1.1 200 OK application/pdf 2268191
12/07-16 HTTP/1.1 200 OK application/pdf 2268191
12/07-16 HTTP/1.1 200 OK application/pdf 2268191
13/07-16 HTTP/1.1 200 OK application/pdf 2268191
13/07-16 HTTP/1.1 200 OK application/pdf 2268191
13/07-16 HTTP/1.1 200 OK application/pdf 2268191
13/07-16 HTTP/1.1 200 OK application/pdf 2268191
13/07-16 HTTP/1.1 200 OK application/pdf 2268191
14/07-16 HTTP/1.1 200 OK application/pdf 2268191
14/07-16 HTTP/1.1 200 OK application/pdf 2268191
14/07-16 HTTP/1.1 200 OK application/pdf 2268191
14/07-16 HTTP/1.1 200 OK application/pdf 2268191
14/07-16 HTTP/1.1 200 OK application/pdf 2268191
15/07-16 HTTP/1.1 200 OK application/pdf 2268191
15/07-16 HTTP/1.1 200 OK application/pdf 2268191
15/07-16 HTTP/1.1 200 OK application/pdf 2268191
15/07-16 HTTP/1.1 200 OK application/pdf 2268191
15/07-16 HTTP/1.1 200 OK application/pdf 2268191
16/07-16 HTTP/1.1 200 OK application/pdf 2268191
16/07-16 HTTP/1.1 200 OK application/pdf 2268191
16/07-16 HTTP/1.1 200 OK application/pdf 2268191
16/07-16 HTTP/1.1 200 OK application/pdf 2268191
16/07-16 HTTP/1.1 200 OK application/pdf 2268191
17/07-16 HTTP/1.1 200 OK application/pdf 2268191
17/07-16 HTTP/1.1 200 OK application/pdf 2268191
17/07-16 HTTP/1.1 200 OK application/pdf 2268191
17/07-16 HTTP/1.1 200 OK application/pdf 2268191
17/07-16 HTTP/1.1 200 OK application/pdf 2268191
18/07-16 HTTP/1.1 200 OK application/pdf 2268191
18/07-16 HTTP/1.1 200 OK application/pdf 2268191
18/07-16 HTTP/1.1 200 OK application/pdf 2268191
18/07-16 HTTP/1.1 200 OK application/pdf 2268191
18/07-16 HTTP/1.1 200 OK application/pdf 2268191
18/07-16 HTTP/1.1 200 OK application/pdf 2268191
19/07-16 HTTP/1.1 200 OK application/pdf 2268191
19/07-16 HTTP/1.1 200 OK application/pdf 2268191
19/07-16 HTTP/1.1 200 OK application/pdf 2268191
19/07-16 HTTP/1.1 200 OK application/pdf 2268191
19/07-16 HTTP/1.1 200 OK application/pdf 2268191
20/07-16 HTTP/1.1 200 OK application/pdf 2268191
20/07-16 HTTP/1.1 200 OK application/pdf 2268191
20/07-16 HTTP/1.1 200 OK application/pdf 2268191
20/07-16 HTTP/1.1 200 OK application/pdf 2268191
20/07-16 HTTP/1.1 200 OK application/pdf 2268191
21/07-16 HTTP/1.1 200 OK application/pdf 2268191
21/07-16 HTTP/1.1 200 OK application/pdf 2268191
21/07-16 HTTP/1.1 200 OK application/pdf 2268191
21/07-16 HTTP/1.1 200 OK application/pdf 2268191
21/07-16 HTTP/1.1 200 OK application/pdf 2268191
22/07-16 HTTP/1.1 200 OK application/pdf 2268191
22/07-16 HTTP/1.1 200 OK application/pdf 2268191
22/07-16 HTTP/1.1 200 OK application/pdf 2268191
22/07-16 HTTP/1.1 200 OK application/pdf 2268191
22/07-16 HTTP/1.1 200 OK application/pdf 2268191
23/07-16 HTTP/1.1 200 OK application/pdf 2268191
23/07-16 HTTP/1.1 200 OK application/pdf 2268191
23/07-16 HTTP/1.1 200 OK application/pdf 2268191
23/07-16 HTTP/1.1 200 OK application/pdf 2268191
23/07-16 HTTP/1.1 200 OK application/pdf 2268191
24/07-16 HTTP/1.1 200 OK application/pdf 2268191
24/07-16 HTTP/1.1 200 OK application/pdf 2268191
24/07-16 HTTP/1.1 200 OK application/pdf 2268191
24/07-16 HTTP/1.1 200 OK application/pdf 2268191
24/07-16 HTTP/1.1 200 OK application/pdf 2268191
25/07-16 HTTP/1.1 200 OK application/pdf 2268191
25/07-16 HTTP/1.1 200 OK application/pdf 2268191
25/07-16 HTTP/1.1 200 OK application/pdf 2268191
25/07-16 HTTP/1.1 200 OK application/pdf 2268191
25/07-16 HTTP/1.1 200 OK application/pdf 2268191
26/07-16 HTTP/1.1 200 OK application/pdf 2268191
26/07-16 HTTP/1.1 200 OK application/pdf 2268191
26/07-16 HTTP/1.1 200 OK application/pdf 2268191
26/07-16 HTTP/1.1 200 OK application/pdf 2268191
26/07-16 HTTP/1.1 200 OK application/pdf 2268191
27/07-16 HTTP/1.1 200 OK application/pdf 2268191
27/07-16 HTTP/1.1 200 OK application/pdf 2268191
27/07-16 HTTP/1.1 200 OK application/pdf 2268191
27/07-16 HTTP/1.1 200 OK application/pdf 2268191
27/07-16 HTTP/1.1 200 OK application/pdf 2268191
28/07-16 HTTP/1.1 200 OK application/pdf 2268191
28/07-16 HTTP/1.1 200 OK application/pdf 2268191
28/07-16 HTTP/1.1 200 OK application/pdf 2268191
28/07-16 HTTP/1.1 200 OK application/pdf 2268191
28/07-16 HTTP/1.1 200 OK application/pdf 2268191
29/07-16 HTTP/1.1 200 OK application/pdf 2268191
29/07-16 HTTP/1.1 200 OK application/pdf 2268191
29/07-16 HTTP/1.1 200 OK application/pdf 2268191
29/07-16 HTTP/1.1 200 OK application/pdf 2268191
29/07-16 HTTP/1.1 200 OK application/pdf 2268191
30/07-16 HTTP/1.1 200 OK application/pdf 2268191
30/07-16 HTTP/1.1 200 OK application/pdf 2268191
30/07-16 HTTP/1.1 200 OK application/pdf 2268191
30/07-16 HTTP/1.1 200 OK application/pdf 2268191
30/07-16 HTTP/1.1 200 OK application/pdf 2268191
31/07-16 HTTP/1.1 200 OK application/pdf 2268191
31/07-16 HTTP/1.1 200 OK application/pdf 2268191
31/07-16 HTTP/1.1 200 OK application/pdf 2268191
31/07-16 HTTP/1.1 200 OK application/pdf 2268191
31/07-16 HTTP/1.1 200 OK application/pdf 2268191
01/08-16 HTTP/1.1 200 OK application/pdf 2268191
01/08-16 HTTP/1.1 200 OK application/pdf 2268191
01/08-16 HTTP/1.1 200 OK application/pdf 2268191
01/08-16 HTTP/1.1 200 OK application/pdf 2268191
01/08-16 HTTP/1.1 200 OK application/pdf 2268191
02/08-16 HTTP/1.1 200 OK application/pdf 2268191
02/08-16 HTTP/1.1 200 OK application/pdf 2268191
02/08-16 HTTP/1.1 200 OK application/pdf 2268191
02/08-16 HTTP/1.1 200 OK application/pdf 2268191
03/08-16 HTTP/1.1 200 OK application/pdf 2268191
03/08-16 HTTP/1.1 200 OK application/pdf 2268191
03/08-16 HTTP/1.1 200 OK application/pdf 2268191
03/08-16 HTTP/1.1 200 OK application/pdf 2268191
03/08-16 HTTP/1.1 200 OK application/pdf 2268191
04/08-16 HTTP/1.1 200 OK application/pdf 2268191
04/08-16 HTTP/1.1 200 OK application/pdf 2268191
05/08-16 HTTP/1.1 200 OK application/pdf 2268191
06/08-16 HTTP/1.1 200 OK application/pdf 2268191
06/08-16 HTTP/1.1 200 OK application/pdf 2268191
07/08-16 HTTP/1.1 200 OK application/pdf 2268191
07/08-16 HTTP/1.1 200 OK application/pdf 2268191
08/08-16 HTTP/1.1 200 OK application/pdf 2268191
09/08-16 HTTP/1.1 200 OK application/pdf 2268191
09/08-16 HTTP/1.1 200 OK application/pdf 2268191
10/08-16 HTTP/1.1 200 OK application/pdf 2268191
11/08-16 HTTP/1.1 200 OK application/pdf 2268191
11/08-16 HTTP/1.1 200 OK application/pdf 2268191
12/08-16 HTTP/1.1 200 OK application/pdf 2268191
12/08-16 HTTP/1.1 200 OK application/pdf 2268191
13/08-16 HTTP/1.1 200 OK application/pdf 2268191
13/08-16 HTTP/1.1 200 OK application/pdf 2268191
13/08-16 HTTP/1.1 200 OK application/pdf 2268191
13/08-16 HTTP/1.1 200 OK application/pdf 2268191
14/08-16 HTTP/1.1 200 OK application/pdf 2268191
14/08-16 HTTP/1.1 200 OK application/pdf 2268191
14/08-16 HTTP/1.1 200 OK application/pdf 2268191
14/08-16 HTTP/1.1 200 OK application/pdf 2268191
15/08-16 HTTP/1.1 200 OK application/pdf 2268191
15/08-16 HTTP/1.1 200 OK application/pdf 2268191
15/08-16 HTTP/1.1 200 OK application/pdf 2268191
15/08-16 HTTP/1.1 200 OK application/pdf 2268191
15/08-16 HTTP/1.1 200 OK application/pdf 2268191
15/08-16 HTTP/1.1 200 OK application/pdf 2268191
16/08-16 HTTP/1.1 200 OK application/pdf 2268191
16/08-16 HTTP/1.1 200 OK application/pdf 2268191
16/08-16 HTTP/1.1 200 OK application/pdf 2268191
16/08-16 HTTP/1.1 200 OK application/pdf 2268191
17/08-16 HTTP/1.1 200 OK application/pdf 2268191
17/08-16 HTTP/1.1 200 OK application/pdf 2268191
17/08-16 HTTP/1.1 200 OK application/pdf 2268191
17/08-16 HTTP/1.1 200 OK application/pdf 2268191
17/08-16 HTTP/1.1 200 OK application/pdf 2268191
18/08-16 HTTP/1.1 200 OK application/pdf 2268191
18/08-16 HTTP/1.1 200 OK application/pdf 2268191
18/08-16 HTTP/1.1 200 OK application/pdf 2268191
18/08-16 HTTP/1.1 200 OK application/pdf 2268191
18/08-16 HTTP/1.1 200 OK application/pdf 2268191
19/08-16 HTTP/1.1 200 OK application/pdf 2268191
19/08-16 HTTP/1.1 200 OK application/pdf 2268191
19/08-16 HTTP/1.1 200 OK application/pdf 2268191
19/08-16 HTTP/1.1 200 OK application/pdf 2268191
19/08-16 HTTP/1.1 200 OK application/pdf 2268191
20/08-16 HTTP/1.1 200 OK application/pdf 2268191
20/08-16 HTTP/1.1 200 OK application/pdf 2268191
20/08-16 HTTP/1.1 200 OK application/pdf 2268191
20/08-16 HTTP/1.1 200 OK application/pdf 2268191
20/08-16 HTTP/1.1 200 OK application/pdf 2268191
21/08-16 HTTP/1.1 200 OK application/pdf 2268191
21/08-16 HTTP/1.1 200 OK application/pdf 2268191
21/08-16 HTTP/1.1 200 OK application/pdf 2268191
21/08-16 HTTP/1.1 200 OK application/pdf 2268191
21/08-16 HTTP/1.1 200 OK application/pdf 2268191
22/08-16 HTTP/1.1 200 OK application/pdf 2268191
22/08-16 HTTP/1.1 200 OK application/pdf 2268191
22/08-16 HTTP/1.1 200 OK application/pdf 2268191
22/08-16 HTTP/1.1 200 OK application/pdf 2268191
22/08-16 HTTP/1.1 200 OK application/pdf 2268191
23/08-16 HTTP/1.1 200 OK application/pdf 2268191
23/08-16 HTTP/1.1 200 OK application/pdf 2268191
23/08-16 HTTP/1.1 200 OK application/pdf 2268191
23/08-16 HTTP/1.1 200 OK application/pdf 2268191
24/08-16 HTTP/1.1 200 OK application/pdf 2268191
24/08-16 HTTP/1.1 200 OK application/pdf 2268191
24/08-16 HTTP/1.1 200 OK application/pdf 2268191
24/08-16 HTTP/1.1 200 OK application/pdf 2268191
24/08-16 HTTP/1.1 200 OK application/pdf 2268191
25/08-16 HTTP/1.1 200 OK application/pdf 2268191
25/08-16 HTTP/1.1 200 OK application/pdf 2268191
25/08-16 HTTP/1.1 200 OK application/pdf 2268191
25/08-16 HTTP/1.1 200 OK application/pdf 2268191
25/08-16 HTTP/1.1 200 OK application/pdf 2268191
26/08-16 HTTP/1.1 200 OK application/pdf 2268191
26/08-16 HTTP/1.1 200 OK application/pdf 2268191
26/08-16 HTTP/1.1 200 OK application/pdf 2268191
26/08-16 HTTP/1.1 200 OK application/pdf 2268191
26/08-16 HTTP/1.1 200 OK application/pdf 2268191
27/08-16 HTTP/1.1 200 OK application/pdf 2268191
27/08-16 HTTP/1.1 200 OK application/pdf 2268191
27/08-16 HTTP/1.1 200 OK application/pdf 2268191
27/08-16 HTTP/1.1 200 OK application/pdf 2268191
28/08-16 HTTP/1.1 200 OK application/pdf 2268191
28/08-16 HTTP/1.1 200 OK application/pdf 2268191
28/08-16 HTTP/1.1 200 OK application/pdf 2268191
28/08-16 HTTP/1.1 200 OK application/pdf 2268191
28/08-16 HTTP/1.1 200 OK application/pdf 2268191
29/08-16 HTTP/1.1 200 OK application/pdf 2268191
29/08-16 HTTP/1.1 200 OK application/pdf 2268191
29/08-16 HTTP/1.1 200 OK application/pdf 2268191
29/08-16 HTTP/1.1 200 OK application/pdf 2268191
29/08-16 HTTP/1.1 200 OK application/pdf 2268191
30/08-16 HTTP/1.1 200 OK application/pdf 2268191
30/08-16 HTTP/1.1 200 OK application/pdf 2268191
30/08-16 HTTP/1.1 200 OK application/pdf 2268191
30/08-16 HTTP/1.1 200 OK application/pdf 2268191
31/08-16 HTTP/1.1 200 OK application/pdf 2268191
31/08-16 HTTP/1.1 200 OK application/pdf 2268191
31/08-16 HTTP/1.1 200 OK application/pdf 2268191
31/08-16 HTTP/1.1 200 OK application/pdf 2268191
31/08-16 HTTP/1.1 200 OK application/pdf 2268191
01/09-16 HTTP/1.1 200 OK application/pdf 2268191
01/09-16 HTTP/1.1 200 OK application/pdf 2268191
01/09-16 HTTP/1.1 200 OK application/pdf 2268191
01/09-16 HTTP/1.1 200 OK application/pdf 2268191
01/09-16 HTTP/1.1 200 OK application/pdf 2268191
02/09-16 HTTP/1.1 200 OK application/pdf 2268191
02/09-16 HTTP/1.1 200 OK application/pdf 2268191
02/09-16 HTTP/1.1 200 OK application/pdf 2268191
02/09-16 HTTP/1.1 200 OK application/pdf 2268191
02/09-16 HTTP/1.1 200 OK application/pdf 2268191
03/09-16 HTTP/1.1 200 OK application/pdf 2268191
03/09-16 HTTP/1.1 200 OK application/pdf 2268191
03/09-16 HTTP/1.1 200 OK application/pdf 2268191
03/09-16 HTTP/1.1 200 OK application/pdf 2268191
03/09-16 HTTP/1.1 200 OK application/pdf 2268191
04/09-16 HTTP/1.1 200 OK application/pdf 2268191
04/09-16 HTTP/1.1 200 OK application/pdf 2268191
04/09-16 HTTP/1.1 200 OK application/pdf 2268191
04/09-16 HTTP/1.1 200 OK application/pdf 2268191
05/09-16 HTTP/1.1 200 OK application/pdf 2268191
05/09-16 HTTP/1.1 200 OK application/pdf 2268191
05/09-16 HTTP/1.1 200 OK application/pdf 2268191
05/09-16 HTTP/1.1 200 OK application/pdf 2268191
05/09-16 HTTP/1.1 200 OK application/pdf 2268191
06/09-16 HTTP/1.1 200 OK application/pdf 2268191
06/09-16 HTTP/1.1 200 OK application/pdf 2268191
06/09-16 HTTP/1.1 200 OK application/pdf 2268191
06/09-16 HTTP/1.1 200 OK application/pdf 2268191
06/09-16 HTTP/1.1 200 OK application/pdf 2268191
07/09-16 HTTP/1.1 200 OK application/pdf 2268191
07/09-16 HTTP/1.1 200 OK application/pdf 2268191
07/09-16 HTTP/1.1 200 OK application/pdf 2268191
07/09-16 HTTP/1.1 200 OK application/pdf 2268191
07/09-16 HTTP/1.1 200 OK application/pdf 2268191
08/09-16 HTTP/1.1 200 OK application/pdf 2268191
08/09-16 HTTP/1.1 200 OK application/pdf 2268191
08/09-16 HTTP/1.1 200 OK application/pdf 2268191
08/09-16 HTTP/1.1 200 OK application/pdf 2268191
08/09-16 HTTP/1.1 200 OK application/pdf 2268191
09/09-16 HTTP/1.1 200 OK application/pdf 2268191
09/09-16 HTTP/1.1 200 OK application/pdf 2268191
09/09-16 HTTP/1.1 200 OK application/pdf 2268191
09/09-16 HTTP/1.1 200 OK application/pdf 2268191
09/09-16 HTTP/1.1 200 OK application/pdf 2268191
10/09-16 HTTP/1.1 200 OK application/pdf 2268191
10/09-16 HTTP/1.1 200 OK application/pdf 2268191
10/09-16 HTTP/1.1 200 OK application/pdf 2268191
10/09-16 HTTP/1.1 200 OK application/pdf 2268191
11/09-16 HTTP/1.1 200 OK application/pdf 2268191
11/09-16 HTTP/1.1 200 OK application/pdf 2268191
11/09-16 HTTP/1.1 200 OK application/pdf 2268191
11/09-16 HTTP/1.1 200 OK application/pdf 2268191
11/09-16 HTTP/1.1 200 OK application/pdf 2268191
12/09-16 HTTP/1.1 200 OK application/pdf 2268191
12/09-16 HTTP/1.1 200 OK application/pdf 2268191
12/09-16 HTTP/1.1 200 OK application/pdf 2268191
12/09-16 HTTP/1.1 200 OK application/pdf 2268191
12/09-16 HTTP/1.1 200 OK application/pdf 2268191
13/09-16 HTTP/1.1 200 OK application/pdf 2268191
13/09-16 HTTP/1.1 200 OK application/pdf 2268191
13/09-16 HTTP/1.1 200 OK application/pdf 2268191
13/09-16 HTTP/1.1 200 OK application/pdf 2268191
14/09-16 HTTP/1.1 200 OK application/pdf 2268191
14/09-16 HTTP/1.1 200 OK application/pdf 2268191
14/09-16 HTTP/1.1 200 OK application/pdf 2268191
14/09-16 HTTP/1.1 200 OK application/pdf 2268191
14/09-16 HTTP/1.1 200 OK application/pdf 2268191
15/09-16 HTTP/1.1 200 OK application/pdf 2268191
15/09-16 HTTP/1.1 200 OK application/pdf 2268191
15/09-16 HTTP/1.1 200 OK application/pdf 2268191
15/09-16 HTTP/1.1 200 OK application/pdf 2268191
15/09-16 HTTP/1.1 200 OK application/pdf 2268191
16/09-16 HTTP/1.1 200 OK application/pdf 2268191
16/09-16 HTTP/1.1 200 OK application/pdf 2268191
16/09-16 HTTP/1.1 200 OK application/pdf 2268191
16/09-16 HTTP/1.1 200 OK application/pdf 2268191
17/09-16 HTTP/1.1 200 OK application/pdf 2268191
17/09-16 HTTP/1.1 200 OK application/pdf 2268191
17/09-16 HTTP/1.1 200 OK application/pdf 2268191
17/09-16 HTTP/1.1 200 OK application/pdf 2268191
17/09-16 HTTP/1.1 200 OK application/pdf 2268191
18/09-16 HTTP/1.1 200 OK application/pdf 2268191
18/09-16 HTTP/1.1 200 OK application/pdf 2268191
18/09-16 HTTP/1.1 200 OK application/pdf 2268191
18/09-16 HTTP/1.1 200 OK application/pdf 2268191
18/09-16 HTTP/1.1 200 OK application/pdf 2268191
19/09-16 HTTP/1.1 200 OK application/pdf 2268191
19/09-16 HTTP/1.1 200 OK application/pdf 2268191
19/09-16 HTTP/1.1 200 OK application/pdf 2268191
19/09-16 HTTP/1.1 200 OK application/pdf 2268191
20/09-16 HTTP/1.1 200 OK application/pdf 2268191
20/09-16 HTTP/1.1 200 OK application/pdf 2268191
20/09-16 HTTP/1.1 200 OK application/pdf 2268191
20/09-16 HTTP/1.1 200 OK application/pdf 2268191
20/09-16 HTTP/1.1 200 OK application/pdf 2268191
21/09-16 HTTP/1.1 200 OK application/pdf 2268191
21/09-16 HTTP/1.1 200 OK application/pdf 2268191
21/09-16 HTTP/1.1 200 OK application/pdf 2268191
21/09-16 HTTP/1.1 200 OK application/pdf 2268191
22/09-16 HTTP/1.1 200 OK application/pdf 2268191
22/09-16 HTTP/1.1 200 OK application/pdf 2268191
22/09-16 HTTP/1.1 200 OK application/pdf 2268191
22/09-16 HTTP/1.1 200 OK application/pdf 2268191
22/09-16 HTTP/1.1 200 OK application/pdf 2268191
23/09-16 HTTP/1.1 200 OK application/pdf 2268191
23/09-16 HTTP/1.1 200 OK application/pdf 2268191
23/09-16 HTTP/1.1 200 OK application/pdf 2268191
24/09-16 HTTP/1.1 200 OK application/pdf 2268191
24/09-16 HTTP/1.1 200 OK application/pdf 2268191
24/09-16 HTTP/1.1 200 OK application/pdf 2268191
24/09-16 HTTP/1.1 200 OK application/pdf 2268191
25/09-16 HTTP/1.1 200 OK application/pdf 2268191
25/09-16 HTTP/1.1 200 OK application/pdf 2268191
25/09-16 HTTP/1.1 200 OK application/pdf 2268191
25/09-16 HTTP/1.1 200 OK application/pdf 2268191
26/09-16 HTTP/1.1 200 OK application/pdf 2268191
26/09-16 HTTP/1.1 200 OK application/pdf 2268191
26/09-16 HTTP/1.1 200 OK application/pdf 2268191
26/09-16 HTTP/1.1 200 OK application/pdf 2268191
26/09-16 HTTP/1.1 200 OK application/pdf 2268191
27/09-16 HTTP/1.1 200 OK application/pdf 2268191
27/09-16 HTTP/1.1 200 OK application/pdf 2268191
27/09-16 HTTP/1.1 200 OK application/pdf 2268191
27/09-16 HTTP/1.1 200 OK application/pdf 2268191
28/09-16 HTTP/1.1 200 OK application/pdf 2268191
28/09-16 HTTP/1.1 200 OK application/pdf 2268191
28/09-16 HTTP/1.1 200 OK application/pdf 2268191
28/09-16 HTTP/1.1 200 OK application/pdf 2268191
28/09-16 HTTP/1.1 200 OK application/pdf 2268191
29/09-16 HTTP/1.1 200 OK application/pdf 2268191
29/09-16 HTTP/1.1 200 OK application/pdf 2268191
29/09-16 HTTP/1.1 200 OK application/pdf 2268191
29/09-16 HTTP/1.1 200 OK application/pdf 2268191
30/09-16 HTTP/1.1 200 OK application/pdf 2268191
30/09-16 HTTP/1.1 200 OK application/pdf 2268191
30/09-16 HTTP/1.1 200 OK application/pdf 2268191
30/09-16 HTTP/1.1 200 OK application/pdf 2268191
01/10-16 HTTP/1.1 200 OK application/pdf 2268191
01/10-16 HTTP/1.1 200 OK application/pdf 2268191
01/10-16 HTTP/1.1 200 OK application/pdf 2268191
01/10-16 HTTP/1.1 200 OK application/pdf 2268191
01/10-16 HTTP/1.1 200 OK application/pdf 2268191
02/10-16 HTTP/1.1 200 OK application/pdf 2268191
02/10-16 HTTP/1.1 200 OK application/pdf 2268191
02/10-16 HTTP/1.1 200 OK application/pdf 2268191
02/10-16 HTTP/1.1 200 OK application/pdf 2268191
02/10-16 HTTP/1.1 200 OK application/pdf 2268191
03/10-16 HTTP/1.1 200 OK application/pdf 2268191
03/10-16 HTTP/1.1 200 OK application/pdf 2268191
03/10-16 HTTP/1.1 200 OK application/pdf 2268191
03/10-16 HTTP/1.1 200 OK application/pdf 2268191
03/10-16 HTTP/1.1 200 OK application/pdf 2268191
04/10-16 HTTP/1.1 200 OK application/pdf 2268191
04/10-16 HTTP/1.1 200 OK application/pdf 2268191
04/10-16 HTTP/1.1 200 OK application/pdf 2268191
04/10-16 HTTP/1.1 200 OK application/pdf 2268191
05/10-16 HTTP/1.1 200 OK application/pdf 2268191
05/10-16 HTTP/1.1 200 OK application/pdf 2268191
05/10-16 HTTP/1.1 200 OK application/pdf 2268191
05/10-16 HTTP/1.1 200 OK application/pdf 2268191
06/10-16 HTTP/1.1 200 OK application/pdf 2268191
06/10-16 HTTP/1.1 200 OK application/pdf 2268191
06/10-16 HTTP/1.1 200 OK application/pdf 2268191
07/10-16 HTTP/1.1 200 OK application/pdf 2268191
07/10-16 HTTP/1.1 200 OK application/pdf 2268191
07/10-16 HTTP/1.1 200 OK application/pdf 2268191
08/10-16 HTTP/1.1 200 OK application/pdf 2268191
08/10-16 HTTP/1.1 200 OK application/pdf 2268191
08/10-16 HTTP/1.1 200 OK application/pdf 2268191
08/10-16 HTTP/1.1 200 OK application/pdf 2268191
09/10-16 HTTP/1.1 200 OK application/pdf 2268191
09/10-16 HTTP/1.1 200 OK application/pdf 2268191
09/10-16 HTTP/1.1 200 OK application/pdf 2268191
09/10-16 HTTP/1.1 200 OK application/pdf 2268191
10/10-16 HTTP/1.1 200 OK application/pdf 2268191
10/10-16 HTTP/1.1 200 OK application/pdf 2268191
10/10-16 HTTP/1.1 200 OK application/pdf 2268191
10/10-16 HTTP/1.1 200 OK application/pdf 2268191
11/10-16 HTTP/1.1 200 OK application/pdf 2268191
11/10-16 HTTP/1.1 200 OK application/pdf 2268191
11/10-16 HTTP/1.1 200 OK application/pdf 2268191
11/10-16 HTTP/1.1 200 OK application/pdf 2268191
12/10-16 HTTP/1.1 200 OK application/pdf 2268191
12/10-16 HTTP/1.1 200 OK application/pdf 2268191
12/10-16 HTTP/1.1 200 OK application/pdf 2268191
12/10-16 HTTP/1.1 200 OK application/pdf 2268191
12/10-16 HTTP/1.1 200 OK application/pdf 2268191
13/10-16 HTTP/1.1 200 OK application/pdf 2268191
13/10-16 HTTP/1.1 200 OK application/pdf 2268191
14/10-16 HTTP/1.1 200 OK application/pdf 2268191
14/10-16 HTTP/1.1 200 OK application/pdf 2268191
14/10-16 HTTP/1.1 200 OK application/pdf 2268191
14/10-16 HTTP/1.1 200 OK application/pdf 2268191
14/10-16 HTTP/1.1 200 OK application/pdf 2268191
15/10-16 N/A 0
15/10-16 HTTP/1.1 200 OK application/pdf 2268191
15/10-16 HTTP/1.1 200 OK application/pdf 2268191
15/10-16 HTTP/1.1 200 OK application/pdf 2268191
16/10-16 HTTP/1.1 200 OK application/pdf 2268191
16/10-16 HTTP/1.1 200 OK application/pdf 2268191
16/10-16 HTTP/1.1 200 OK application/pdf 2268191
16/10-16 HTTP/1.1 200 OK application/pdf 2268191
17/10-16 HTTP/1.1 200 OK application/pdf 2268191
17/10-16 HTTP/1.1 200 OK application/pdf 2268191
17/10-16 HTTP/1.1 200 OK application/pdf 2268191
18/10-16 HTTP/1.1 200 OK application/pdf 2268191
18/10-16 HTTP/1.1 200 OK application/pdf 2268191
18/10-16 HTTP/1.1 200 OK application/pdf 2268191
18/10-16 HTTP/1.1 200 OK application/pdf 2268191
19/10-16 HTTP/1.1 200 OK application/pdf 2268191
19/10-16 HTTP/1.1 200 OK application/pdf 2268191
19/10-16 HTTP/1.1 200 OK application/pdf 2268191
19/10-16 HTTP/1.1 200 OK application/pdf 2268191
20/10-16 HTTP/1.1 200 OK application/pdf 2268191
20/10-16 HTTP/1.1 200 OK application/pdf 2268191
20/10-16 HTTP/1.1 200 OK application/pdf 2268191
21/10-16 HTTP/1.1 200 OK application/pdf 2268191
21/10-16 HTTP/1.1 200 OK application/pdf 2268191
21/10-16 HTTP/1.1 200 OK application/pdf 2268191
22/10-16 HTTP/1.1 200 OK application/pdf 2268191
22/10-16 HTTP/1.1 200 OK application/pdf 2268191
22/10-16 HTTP/1.1 200 OK application/pdf 2268191
22/10-16 HTTP/1.1 200 OK application/pdf 2268191
23/10-16 HTTP/1.1 200 OK application/pdf 2268191
23/10-16 HTTP/1.1 200 OK application/pdf 2268191
23/10-16 HTTP/1.1 200 OK application/pdf 2268191
23/10-16 HTTP/1.1 200 OK application/pdf 2268191
24/10-16 HTTP/1.1 200 OK application/pdf 2268191
24/10-16 HTTP/1.1 200 OK application/pdf 2268191
25/10-16 HTTP/1.1 200 OK application/pdf 2268191
25/10-16 HTTP/1.1 200 OK application/pdf 2268191
26/10-16 HTTP/1.1 200 OK application/pdf 2268191
27/10-16 HTTP/1.1 200 OK application/pdf 2268191
27/10-16 HTTP/1.1 200 OK application/pdf 2268191
27/10-16 HTTP/1.1 200 OK application/pdf 2268191
28/10-16 HTTP/1.1 200 OK application/pdf 2268191
28/10-16 HTTP/1.1 200 OK application/pdf 2268191
29/10-16 HTTP/1.1 200 OK application/pdf 2268191
29/10-16 HTTP/1.1 200 OK application/pdf 2268191
30/10-16 N/A 0
30/10-16 HTTP/1.1 200 OK application/pdf 2268191
30/10-16 HTTP/1.1 200 OK application/pdf 2268191
31/10-16 HTTP/1.1 200 OK application/pdf 2268191
01/11-16 HTTP/1.1 200 OK application/pdf 2268191
01/11-16 HTTP/1.1 200 OK application/pdf 2268191
02/11-16 HTTP/1.1 200 OK application/pdf 2268191
02/11-16 HTTP/1.1 200 OK application/pdf 2268191
02/11-16 HTTP/1.1 200 OK application/pdf 2268191
03/11-16 HTTP/1.1 200 OK application/pdf 2268191
03/11-16 HTTP/1.1 200 OK application/pdf 2268191
04/11-16 HTTP/1.1 200 OK application/pdf 2268191
04/11-16 HTTP/1.1 200 OK application/pdf 2268191
05/11-16 HTTP/1.1 200 OK application/pdf 2268191
05/11-16 HTTP/1.1 200 OK application/pdf 2268191
05/11-16 HTTP/1.1 200 OK application/pdf 2268191
06/11-16 HTTP/1.1 200 OK application/pdf 2268191
07/11-16 HTTP/1.1 200 OK application/pdf 2268191
07/11-16 HTTP/1.1 200 OK application/pdf 2268191
08/11-16 HTTP/1.1 200 OK application/pdf 2268191
08/11-16 HTTP/1.1 200 OK application/pdf 2268191
09/11-16 HTTP/1.1 200 OK application/pdf 2268191
09/11-16 HTTP/1.1 200 OK application/pdf 2268191
10/11-16 HTTP/1.1 200 OK application/pdf 2268191
10/11-16 HTTP/1.1 200 OK application/pdf 2268191
11/11-16 HTTP/1.1 200 OK application/pdf 2268191
12/11-16 HTTP/1.1 200 OK application/pdf 2268191
13/11-16 HTTP/1.1 200 OK application/pdf 2268191
14/11-16 HTTP/1.1 200 OK application/pdf 2268191
14/11-16 HTTP/1.1 200 OK application/pdf 2268191
14/11-16 HTTP/1.1 200 OK application/pdf 2268191
15/11-16 HTTP/1.1 200 OK application/pdf 2268191
15/11-16 HTTP/1.1 200 OK application/pdf 2268191
15/11-16 HTTP/1.1 200 OK application/pdf 2268191
16/11-16 HTTP/1.1 200 OK application/pdf 2268191
16/11-16 HTTP/1.1 200 OK application/pdf 2268191
17/11-16 HTTP/1.1 200 OK application/pdf 2268191
18/11-16 HTTP/1.1 200 OK application/pdf 2268191
18/11-16 HTTP/1.1 200 OK application/pdf 2268191
18/11-16 HTTP/1.1 200 OK application/pdf 2268191
19/11-16 HTTP/1.1 200 OK application/pdf 2268191
19/11-16 HTTP/1.1 200 OK application/pdf 2268191
20/11-16 HTTP/1.1 200 OK application/pdf 2268191
20/11-16 HTTP/1.1 200 OK application/pdf 2268191
20/11-16 HTTP/1.1 200 OK application/pdf 2268191
21/11-16 HTTP/1.1 200 OK application/pdf 2268191
21/11-16 HTTP/1.1 200 OK application/pdf 2268191
22/11-16 HTTP/1.1 200 OK application/pdf 2268191
22/11-16 HTTP/1.1 200 OK application/pdf 2268191
23/11-16 HTTP/1.1 200 OK application/pdf 2268191
23/11-16 HTTP/1.1 200 OK application/pdf 2268191
23/11-16 HTTP/1.1 200 OK application/pdf 2268191
23/11-16 HTTP/1.1 200 OK application/pdf 2268191
23/11-16 HTTP/1.1 200 OK application/pdf 2268191
24/11-16 HTTP/1.1 200 OK application/pdf 2268191
24/11-16 HTTP/1.1 200 OK application/pdf 2268191
24/11-16 HTTP/1.1 200 OK application/pdf 2268191
24/11-16 HTTP/1.1 200 OK application/pdf 2268191
24/11-16 HTTP/1.1 200 OK application/pdf 2268191
25/11-16 HTTP/1.1 200 OK application/pdf 2268191
25/11-16 HTTP/1.1 200 OK application/pdf 2268191
25/11-16 HTTP/1.1 200 OK application/pdf 2268191
25/11-16 HTTP/1.1 200 OK application/pdf 2268191
26/11-16 HTTP/1.1 200 OK application/pdf 2268191
26/11-16 HTTP/1.1 200 OK application/pdf 2268191
26/11-16 HTTP/1.1 200 OK application/pdf 2268191
26/11-16 HTTP/1.1 200 OK application/pdf 2268191
27/11-16 HTTP/1.1 200 OK application/pdf 2268191
27/11-16 HTTP/1.1 200 OK application/pdf 2268191
27/11-16 HTTP/1.1 200 OK application/pdf 2268191
27/11-16 HTTP/1.1 200 OK application/pdf 2268191
27/11-16 HTTP/1.1 200 OK application/pdf 2268191
28/11-16 HTTP/1.1 200 OK application/pdf 2268191
28/11-16 HTTP/1.1 200 OK application/pdf 2268191
28/11-16 HTTP/1.1 200 OK application/pdf 2268191
28/11-16 HTTP/1.1 200 OK application/pdf 2268191
29/11-16 HTTP/1.1 200 OK application/pdf 2268191
29/11-16 HTTP/1.1 200 OK application/pdf 2268191
29/11-16 HTTP/1.1 200 OK application/pdf 2268191
29/11-16 HTTP/1.1 200 OK application/pdf 2268191
30/11-16 HTTP/1.1 200 OK application/pdf 2268191
30/11-16 HTTP/1.1 200 OK application/pdf 2268191
30/11-16 HTTP/1.1 200 OK application/pdf 2268191
30/11-16 HTTP/1.1 200 OK application/pdf 2268191
30/11-16 HTTP/1.1 200 OK application/pdf 2268191
01/12-16 HTTP/1.1 200 OK application/pdf 2268191
01/12-16 HTTP/1.1 200 OK application/pdf 2268191
01/12-16 HTTP/1.1 200 OK application/pdf 2268191
01/12-16 HTTP/1.1 200 OK application/pdf 2268191
02/12-16 HTTP/1.1 200 OK application/pdf 2268191
02/12-16 HTTP/1.1 200 OK application/pdf 2268191
02/12-16 HTTP/1.1 200 OK application/pdf 2268191
02/12-16 HTTP/1.1 200 OK application/pdf 2268191
02/12-16 HTTP/1.1 200 OK application/pdf 2268191
03/12-16 HTTP/1.1 200 OK application/pdf 2268191
03/12-16 HTTP/1.1 200 OK application/pdf 2268191
03/12-16 HTTP/1.1 200 OK application/pdf 2268191
03/12-16 HTTP/1.1 200 OK application/pdf 2268191
04/12-16 HTTP/1.1 200 OK application/pdf 2268191
04/12-16 HTTP/1.1 200 OK application/pdf 2268191
04/12-16 HTTP/1.1 200 OK application/pdf 2268191
04/12-16 HTTP/1.1 200 OK application/pdf 2268191
04/12-16 HTTP/1.1 200 OK application/pdf 2268191
05/12-16 HTTP/1.1 200 OK application/pdf 2268191
05/12-16 HTTP/1.1 200 OK application/pdf 2268191
05/12-16 HTTP/1.1 200 OK application/pdf 2268191
05/12-16 HTTP/1.1 200 OK application/pdf 2268191
06/12-16 HTTP/1.1 200 OK application/pdf 2268191
06/12-16 HTTP/1.1 200 OK application/pdf 2268191
06/12-16 HTTP/1.1 200 OK application/pdf 2268191
06/12-16 HTTP/1.1 200 OK application/pdf 2268191
06/12-16 HTTP/1.1 200 OK application/pdf 2268191
07/12-16 HTTP/1.1 200 OK application/pdf 2268191
07/12-16 HTTP/1.1 200 OK application/pdf 2268191
07/12-16 HTTP/1.1 200 OK application/pdf 2268191
07/12-16 HTTP/1.1 200 OK application/pdf 2268191
08/12-16 HTTP/1.1 200 OK application/pdf 2268191
08/12-16 HTTP/1.1 200 OK application/pdf 2268191
08/12-16 HTTP/1.1 200 OK application/pdf 2268191
08/12-16 HTTP/1.1 200 OK application/pdf 2268191
08/12-16 HTTP/1.1 200 OK application/pdf 2268191
09/12-16 HTTP/1.1 200 OK application/pdf 2268191
09/12-16 HTTP/1.1 200 OK application/pdf 2268191
09/12-16 HTTP/1.1 200 OK application/pdf 2268191
09/12-16 HTTP/1.1 200 OK application/pdf 2268191
10/12-16 HTTP/1.1 200 OK application/pdf 2268191
10/12-16 HTTP/1.1 200 OK application/pdf 2268191
10/12-16 HTTP/1.1 200 OK application/pdf 2268191
10/12-16 HTTP/1.1 200 OK application/pdf 2268191
11/12-16 HTTP/1.1 200 OK application/pdf 2268191
11/12-16 HTTP/1.1 200 OK application/pdf 2268191
11/12-16 HTTP/1.1 200 OK application/pdf 2268191
11/12-16 HTTP/1.1 200 OK application/pdf 2268191
11/12-16 HTTP/1.1 200 OK application/pdf 2268191
12/12-16 HTTP/1.1 200 OK application/pdf 2268191
12/12-16 HTTP/1.1 200 OK application/pdf 2268191
12/12-16 HTTP/1.1 200 OK application/pdf 2268191
12/12-16 HTTP/1.1 200 OK application/pdf 2268191
13/12-16 HTTP/1.1 200 OK application/pdf 2268191
13/12-16 HTTP/1.1 200 OK application/pdf 2268191
13/12-16 HTTP/1.1 200 OK application/pdf 2268191
13/12-16 HTTP/1.1 200 OK application/pdf 2268191
14/12-16 HTTP/1.1 200 OK application/pdf 2268191
14/12-16 HTTP/1.1 200 OK application/pdf 2268191
14/12-16 HTTP/1.1 200 OK application/pdf 2268191
14/12-16 HTTP/1.1 200 OK application/pdf 2268191
15/12-16 HTTP/1.1 200 OK application/pdf 2268191
15/12-16 HTTP/1.1 200 OK application/pdf 2268191
15/12-16 HTTP/1.1 200 OK application/pdf 2268191
15/12-16 HTTP/1.1 200 OK application/pdf 2268191
15/12-16 HTTP/1.1 200 OK application/pdf 2268191
16/12-16 HTTP/1.1 200 OK application/pdf 2268191
16/12-16 HTTP/1.1 200 OK application/pdf 2268191
16/12-16 HTTP/1.1 200 OK application/pdf 2268191
16/12-16 HTTP/1.1 200 OK application/pdf 2268191
17/12-16 HTTP/1.1 200 OK application/pdf 2268191
17/12-16 HTTP/1.1 200 OK application/pdf 2268191
17/12-16 HTTP/1.1 200 OK application/pdf 2268191
17/12-16 HTTP/1.1 200 OK application/pdf 2268191
18/12-16 HTTP/1.1 200 OK application/pdf 2268191
18/12-16 HTTP/1.1 200 OK application/pdf 2268191
18/12-16 HTTP/1.1 200 OK application/pdf 2268191
18/12-16 HTTP/1.1 200 OK application/pdf 2268191
19/12-16 HTTP/1.1 200 OK application/pdf 2268191
19/12-16 HTTP/1.1 200 OK application/pdf 2268191
19/12-16 HTTP/1.1 200 OK application/pdf 2268191
19/12-16 HTTP/1.1 200 OK application/pdf 2268191
20/12-16 HTTP/1.1 200 OK application/pdf 2268191
20/12-16 HTTP/1.1 200 OK application/pdf 2268191
20/12-16 HTTP/1.1 200 OK application/pdf 2268191
20/12-16 HTTP/1.1 200 OK application/pdf 2268191
21/12-16 HTTP/1.1 200 OK application/pdf 2268191
21/12-16 HTTP/1.1 200 OK application/pdf 2268191
21/12-16 HTTP/1.1 200 OK application/pdf 2268191
21/12-16 HTTP/1.1 200 OK application/pdf 2268191
22/12-16 HTTP/1.1 200 OK application/pdf 2268191
22/12-16 HTTP/1.1 200 OK application/pdf 2268191
22/12-16 HTTP/1.1 200 OK application/pdf 2268191
22/12-16 HTTP/1.1 200 OK application/pdf 2268191
23/12-16 HTTP/1.1 200 OK application/pdf 2268191
23/12-16 HTTP/1.1 200 OK application/pdf 2268191
23/12-16 HTTP/1.1 200 OK application/pdf 2268191
23/12-16 HTTP/1.1 200 OK application/pdf 2268191
24/12-16 HTTP/1.1 200 OK application/pdf 2268191
24/12-16 HTTP/1.1 200 OK application/pdf 2268191
25/12-16 HTTP/1.1 200 OK application/pdf 2268191
25/12-16 HTTP/1.1 200 OK application/pdf 2268191
25/12-16 HTTP/1.1 200 OK application/pdf 2268191
26/12-16 HTTP/1.1 200 OK application/pdf 2268191
26/12-16 HTTP/1.1 200 OK application/pdf 2268191
26/12-16 HTTP/1.1 200 OK application/pdf 2268191
26/12-16 HTTP/1.1 200 OK application/pdf 2268191
27/12-16 HTTP/1.1 200 OK application/pdf 2268191
27/12-16 HTTP/1.1 200 OK application/pdf 2268191
27/12-16 HTTP/1.1 200 OK application/pdf 2268191
28/12-16 HTTP/1.1 200 OK application/pdf 2268191
28/12-16 HTTP/1.1 200 OK application/pdf 2268191
28/12-16 HTTP/1.1 200 OK application/pdf 2268191
28/12-16 HTTP/1.1 200 OK application/pdf 2268191
29/12-16 HTTP/1.1 200 OK application/pdf 2268191
29/12-16 HTTP/1.1 200 OK application/pdf 2268191
29/12-16 HTTP/1.1 200 OK application/pdf 2268191
29/12-16 HTTP/1.1 200 OK application/pdf 2268191
30/12-16 HTTP/1.1 200 OK application/pdf 2268191
30/12-16 HTTP/1.1 200 OK application/pdf 2268191
30/12-16 N/A 0
31/12-16 HTTP/1.1 200 OK application/pdf 2268191
31/12-16 HTTP/1.1 200 OK application/pdf 2268191
31/12-16 HTTP/1.1 200 OK application/pdf 2268191
31/12-16 HTTP/1.1 200 OK application/pdf 2268191
01/01-17 HTTP/1.1 200 OK application/pdf 2268191
01/01-17 HTTP/1.1 200 OK application/pdf 2268191
01/01-17 HTTP/1.1 200 OK application/pdf 2268191
02/01-17 HTTP/1.1 200 OK application/pdf 2268191
02/01-17 HTTP/1.1 200 OK application/pdf 2268191
02/01-17 HTTP/1.1 200 OK application/pdf 2268191
02/01-17 HTTP/1.1 200 OK application/pdf 2268191
03/01-17 HTTP/1.1 200 OK application/pdf 2268191
03/01-17 HTTP/1.1 200 OK application/pdf 2268191
03/01-17 HTTP/1.1 200 OK application/pdf 2268191
04/01-17 HTTP/1.1 200 OK application/pdf 2268191
04/01-17 HTTP/1.1 200 OK application/pdf 2268191
04/01-17 HTTP/1.1 200 OK application/pdf 2268191
04/01-17 HTTP/1.1 200 OK application/pdf 2268191
05/01-17 HTTP/1.1 200 OK application/pdf 2268191
05/01-17 HTTP/1.1 200 OK application/pdf 2268191
05/01-17 HTTP/1.1 200 OK application/pdf 2268191
06/01-17 HTTP/1.1 200 OK application/pdf 2268191
06/01-17 HTTP/1.1 200 OK application/pdf 2268191
06/01-17 HTTP/1.1 200 OK application/pdf 2268191
07/01-17 HTTP/1.1 200 OK application/pdf 2268191
07/01-17 HTTP/1.1 200 OK application/pdf 2268191
07/01-17 HTTP/1.1 200 OK application/pdf 2268191
07/01-17 HTTP/1.1 200 OK application/pdf 2268191
08/01-17 HTTP/1.1 200 OK application/pdf 2268191
08/01-17 HTTP/1.1 200 OK application/pdf 2268191
08/01-17 HTTP/1.1 200 OK application/pdf 2268191
09/01-17 HTTP/1.1 200 OK application/pdf 2268191
09/01-17 HTTP/1.1 200 OK application/pdf 2268191
09/01-17 HTTP/1.1 200 OK application/pdf 2268191
10/01-17 HTTP/1.1 200 OK application/pdf 2268191
10/01-17 HTTP/1.1 200 OK application/pdf 2268191
10/01-17 HTTP/1.1 200 OK application/pdf 2268191
11/01-17 HTTP/1.1 200 OK application/pdf 2268191
11/01-17 HTTP/1.1 200 OK application/pdf 2268191
11/01-17 HTTP/1.1 200 OK application/pdf 2268191
11/01-17 HTTP/1.1 200 OK application/pdf 2268191
12/01-17 HTTP/1.1 200 OK application/pdf 2268191
12/01-17 HTTP/1.1 200 OK application/pdf 2268191
12/01-17 HTTP/1.1 200 OK application/pdf 2268191
13/01-17 HTTP/1.1 200 OK application/pdf 2268191
13/01-17 HTTP/1.1 200 OK application/pdf 2268191
13/01-17 HTTP/1.1 200 OK application/pdf 2268191
14/01-17 HTTP/1.1 200 OK application/pdf 2268191
14/01-17 HTTP/1.1 200 OK application/pdf 2268191
14/01-17 HTTP/1.1 200 OK application/pdf 2268191
15/01-17 HTTP/1.1 200 OK application/pdf 2268191
15/01-17 HTTP/1.1 200 OK application/pdf 2268191
15/01-17 HTTP/1.1 200 OK application/pdf 2268191
16/01-17 HTTP/1.1 200 OK application/pdf 2268191
16/01-17 HTTP/1.1 200 OK application/pdf 2268191
16/01-17 HTTP/1.1 200 OK application/pdf 2268191
16/01-17 HTTP/1.1 200 OK application/pdf 2268191
17/01-17 HTTP/1.1 200 OK application/pdf 2268191
17/01-17 HTTP/1.1 200 OK application/pdf 2268191
17/01-17 HTTP/1.1 200 OK application/pdf 2268191
18/01-17 HTTP/1.1 200 OK application/pdf 2268191
18/01-17 HTTP/1.1 200 OK application/pdf 2268191
18/01-17 HTTP/1.1 200 OK application/pdf 2268191
19/01-17 HTTP/1.1 200 OK application/pdf 2268191
19/01-17 HTTP/1.1 200 OK application/pdf 2268191
19/01-17 HTTP/1.1 200 OK application/pdf 2268191
20/01-17 HTTP/1.1 200 OK application/pdf 2268191
20/01-17 HTTP/1.1 200 OK application/pdf 2268191
21/01-17 HTTP/1.1 200 OK application/pdf 2268191
21/01-17 HTTP/1.1 200 OK application/pdf 2268191
21/01-17 HTTP/1.1 200 OK application/pdf 2268191
22/01-17 HTTP/1.1 200 OK application/pdf 2268191
22/01-17 HTTP/1.1 200 OK application/pdf 2268191
22/01-17 HTTP/1.1 200 OK application/pdf 2268191
23/01-17 HTTP/1.1 200 OK application/pdf 2268191
23/01-17 HTTP/1.1 200 OK application/pdf 2268191
23/01-17 HTTP/1.1 200 OK application/pdf 2268191
24/01-17 HTTP/1.1 200 OK application/pdf 2268191
24/01-17 HTTP/1.1 200 OK application/pdf 2268191
24/01-17 HTTP/1.1 200 OK application/pdf 2268191
25/01-17 HTTP/1.1 200 OK application/pdf 2268191
25/01-17 HTTP/1.1 200 OK application/pdf 2268191
26/01-17 HTTP/1.1 200 OK application/pdf 2268191
26/01-17 HTTP/1.1 200 OK application/pdf 2268191
26/01-17 HTTP/1.1 200 OK application/pdf 2268191
27/01-17 HTTP/1.1 200 OK application/pdf 2268191
27/01-17 HTTP/1.1 200 OK application/pdf 2268191
27/01-17 HTTP/1.1 200 OK application/pdf 2268191
28/01-17 HTTP/1.1 200 OK application/pdf 2268191
28/01-17 HTTP/1.1 200 OK application/pdf 2268191
29/01-17 HTTP/1.1 200 OK application/pdf 2268191
29/01-17 HTTP/1.1 200 OK application/pdf 2268191
29/01-17 HTTP/1.1 200 OK application/pdf 2268191
30/01-17 HTTP/1.1 200 OK application/pdf 2268191
30/01-17 HTTP/1.1 200 OK application/pdf 2268191
31/01-17 HTTP/1.1 200 OK application/pdf 2268191
31/01-17 HTTP/1.1 200 OK application/pdf 2268191
31/01-17 HTTP/1.1 200 OK application/pdf 2268191
01/02-17 HTTP/1.1 200 OK application/pdf 2268191
01/02-17 HTTP/1.1 200 OK application/pdf 2268191
02/02-17 HTTP/1.1 200 OK application/pdf 2268191
02/02-17 HTTP/1.1 200 OK application/pdf 2268191
02/02-17 HTTP/1.1 200 OK application/pdf 2268191
03/02-17 HTTP/1.1 200 OK application/pdf 2268191
03/02-17 HTTP/1.1 200 OK application/pdf 2268191
04/02-17 HTTP/1.1 200 OK application/pdf 2268191
04/02-17 HTTP/1.1 200 OK application/pdf 2268191
05/02-17 HTTP/1.1 200 OK application/pdf 2268191
05/02-17 HTTP/1.1 200 OK application/pdf 2268191
05/02-17 HTTP/1.1 200 OK application/pdf 2268191
06/02-17 HTTP/1.1 200 OK application/pdf 2268191
06/02-17 HTTP/1.1 200 OK application/pdf 2268191
07/02-17 HTTP/1.1 200 OK application/pdf 2268191
07/02-17 HTTP/1.1 200 OK application/pdf 2268191
07/02-17 HTTP/1.1 200 OK application/pdf 2268191
08/02-17 HTTP/1.1 200 OK application/pdf 2268191
08/02-17 HTTP/1.1 200 OK application/pdf 2268191
09/02-17 HTTP/1.1 200 OK application/pdf 2268191
09/02-17 HTTP/1.1 200 OK application/pdf 2268191
10/02-17 HTTP/1.1 200 OK application/pdf 2268191
10/02-17 HTTP/1.1 200 OK application/pdf 2268191
11/02-17 HTTP/1.1 200 OK application/pdf 2268191
11/02-17 HTTP/1.1 200 OK application/pdf 2268191
11/02-17 HTTP/1.1 200 OK application/pdf 2268191
12/02-17 HTTP/1.1 200 OK application/pdf 2268191
12/02-17 HTTP/1.1 200 OK application/pdf 2268191
13/02-17 HTTP/1.1 200 OK application/pdf 2268191
13/02-17 HTTP/1.1 200 OK application/pdf 2268191
14/02-17 HTTP/1.1 200 OK application/pdf 2268191
14/02-17 HTTP/1.1 200 OK application/pdf 2268191
15/02-17 HTTP/1.1 200 OK application/pdf 2268191
15/02-17 HTTP/1.1 200 OK application/pdf 2268191
15/02-17 HTTP/1.1 200 OK application/pdf 2268191
16/02-17 HTTP/1.1 200 OK application/pdf 2268191
16/02-17 HTTP/1.1 200 OK application/pdf 2268191
17/02-17 HTTP/1.1 200 OK application/pdf 2268191
17/02-17 HTTP/1.1 200 OK application/pdf 2268191
18/02-17 HTTP/1.1 200 OK application/pdf 2268191
18/02-17 HTTP/1.1 200 OK application/pdf 2268191
19/02-17 HTTP/1.1 200 OK application/pdf 2268191
19/02-17 HTTP/1.1 200 OK application/pdf 2268191
20/02-17 HTTP/1.1 200 OK application/pdf 2268191
20/02-17 HTTP/1.1 200 OK application/pdf 2268191
21/02-17 HTTP/1.1 200 OK application/pdf 2268191
21/02-17 HTTP/1.1 200 OK application/pdf 2268191
22/02-17 HTTP/1.1 200 OK application/pdf 2268191
22/02-17 HTTP/1.1 200 OK application/pdf 2268191
22/02-17 HTTP/1.1 200 OK application/pdf 2268191
23/02-17 HTTP/1.1 200 OK application/pdf 2268191
23/02-17 HTTP/1.1 200 OK application/pdf 2268191
24/02-17 HTTP/1.1 200 OK application/pdf 2268191
24/02-17 HTTP/1.1 200 OK application/pdf 2268191
25/02-17 HTTP/1.1 200 OK application/pdf 2268191
25/02-17 HTTP/1.1 200 OK application/pdf 2268191
26/02-17 HTTP/1.1 200 OK application/pdf 2268191
26/02-17 HTTP/1.1 200 OK application/pdf 2268191
27/02-17 HTTP/1.1 200 OK application/pdf 2268191
28/02-17 HTTP/1.1 200 OK application/pdf 2268191
28/02-17 HTTP/1.1 200 OK application/pdf 2268191
01/03-17 HTTP/1.1 200 OK application/pdf 2268191
01/03-17 HTTP/1.1 200 OK application/pdf 2268191
02/03-17 HTTP/1.1 200 OK application/pdf 2268191
02/03-17 HTTP/1.1 200 OK application/pdf 2268191
03/03-17 HTTP/1.1 200 OK application/pdf 2268191
03/03-17 HTTP/1.1 200 OK application/pdf 2268191
04/03-17 HTTP/1.1 200 OK application/pdf 2268191
04/03-17 HTTP/1.1 200 OK application/pdf 2268191
05/03-17 HTTP/1.1 200 OK application/pdf 2268191
06/03-17 HTTP/1.1 200 OK application/pdf 2268191
06/03-17 HTTP/1.1 200 OK application/pdf 2268191
07/03-17 HTTP/1.1 200 OK application/pdf 2268191
09/03-17 HTTP/1.1 200 OK application/pdf 2268191
10/03-17 HTTP/1.1 200 OK application/pdf 2268191
11/03-17 HTTP/1.1 200 OK application/pdf 2268191
13/03-17 HTTP/1.1 200 OK application/pdf 2268191
14/03-17 HTTP/1.1 200 OK application/pdf 2268191
15/03-17 HTTP/1.1 200 OK application/pdf 2268191
16/03-17 HTTP/1.1 200 OK application/pdf 2268191
17/03-17 HTTP/1.1 200 OK application/pdf 2268191
18/03-17 HTTP/1.1 200 OK application/pdf 2268191
19/03-17 HTTP/1.1 200 OK application/pdf 2268191
21/03-17 HTTP/1.1 200 OK application/pdf 2268191
22/03-17 HTTP/1.1 200 OK application/pdf 2268191
23/03-17 HTTP/1.1 200 OK application/pdf 2268191
24/03-17 HTTP/1.1 200 OK application/pdf 2268191
26/03-17 HTTP/1.1 200 OK application/pdf 2268191
27/03-17 HTTP/1.1 200 OK application/pdf 2268191
28/03-17 HTTP/1.1 200 OK application/pdf 2268191
29/03-17 HTTP/1.1 200 OK application/pdf 2268191
30/03-17 HTTP/1.1 200 OK application/pdf 2268191
01/04-17 HTTP/1.1 200 OK application/pdf 2268191
02/04-17 HTTP/1.1 200 OK application/pdf 2268191
03/04-17 HTTP/1.1 200 OK application/pdf 2268191
04/04-17 HTTP/1.1 200 OK application/pdf 2268191
06/04-17 HTTP/1.1 200 OK application/pdf 2268191
07/04-17 HTTP/1.1 200 OK application/pdf 2268191
09/04-17 HTTP/1.1 200 OK application/pdf 2268191
10/04-17 HTTP/1.1 200 OK application/pdf 2268191
11/04-17 HTTP/1.1 200 OK application/pdf 2268191
12/04-17 HTTP/1.1 200 OK application/pdf 2268191
14/04-17 HTTP/1.1 200 OK application/pdf 2268191
15/04-17 HTTP/1.1 200 OK application/pdf 2268191
16/04-17 HTTP/1.1 200 OK application/pdf 2268191
18/04-17 HTTP/1.1 200 OK application/pdf 2268191
19/04-17 HTTP/1.1 200 OK application/pdf 2268191
20/04-17 HTTP/1.1 200 OK application/pdf 2268191
22/04-17 HTTP/1.1 200 OK application/pdf 2268191
23/04-17 HTTP/1.1 200 OK application/pdf 2268191
24/04-17 HTTP/1.1 200 OK application/pdf 2268191
26/04-17 HTTP/1.1 200 OK application/pdf 2268191
27/04-17 HTTP/1.1 200 OK application/pdf 2268191
28/04-17 HTTP/1.1 200 OK application/pdf 2268191
30/04-17 HTTP/1.1 200 OK application/pdf 2268191
01/05-17 HTTP/1.1 200 OK application/pdf 2268191
03/05-17 HTTP/1.1 200 OK application/pdf 2268191
04/05-17 HTTP/1.1 200 OK application/pdf 2268191
06/05-17 HTTP/1.1 200 OK application/pdf 2268191
07/05-17 HTTP/1.1 200 OK application/pdf 2268191
08/05-17 HTTP/1.1 200 OK application/pdf 2268191
10/05-17 HTTP/1.1 200 OK application/pdf 2268191
11/05-17 HTTP/1.1 200 OK application/pdf 2268191
13/05-17 HTTP/1.1 200 OK application/pdf 2268191
14/05-17 HTTP/1.1 200 OK application/pdf 2268191
16/05-17 HTTP/1.1 200 OK application/pdf 2268191
17/05-17 HTTP/1.1 200 OK application/pdf 2268191
19/05-17 HTTP/1.1 200 OK application/pdf 2268191
21/05-17 HTTP/1.1 200 OK application/pdf 2268191
22/05-17 HTTP/1.1 200 OK application/pdf 2268191
24/05-17 HTTP/1.1 200 OK application/pdf 2268191
25/05-17 HTTP/1.1 200 OK application/pdf 2268191
27/05-17 HTTP/1.1 200 OK application/pdf 2268191
29/05-17 HTTP/1.1 200 OK application/pdf 2268191
31/05-17 HTTP/1.1 200 OK application/pdf 2268191
01/06-17 HTTP/1.1 200 OK application/pdf 2268191
03/06-17 HTTP/1.1 200 OK application/pdf 2268191
05/06-17 HTTP/1.1 200 OK application/pdf 2268191
06/06-17 HTTP/1.1 200 OK application/pdf 2268191