Distfile availability status for net/micro_proxy
Maintainer: ehaupt@FreeBSD.org
Status codes:
- numeric values represent RFC 2616 status codes
- NXDOMAIN means that the hostname could not be resolved
- network timeouts result in code 500
It is possible that a failed check could work now. Status codes between 500-599 are transient errors and the status you see represents the period of time when the distfile was checked.
Ports that set DEPRECATED, FETCH_CMD, FETCH_ENV, FETCH_BEFORE_ARGS, FETCH_AFTER_ARGS, or have a do-fetch: target are simply skipped.
All the tables have clickable headers that sort the table by the clicked column.
show bad only, cvsweb, other ports from this maintainer| URL | Checked | Last OK | Status |
|---|---|---|---|
| http://www.acme.com/software/micro_proxy/micro_proxy_30oct2002.tar.gz | 2013-05-25, 16:57:11 | 200 | |
| http://www.bluestop.org/distfiles/micro_proxy_30oct2002.tar.gz | 2013-05-25, 00:16:51 | 200 | |
| http://www.acme.com/software/micro_proxy/ | 2013-05-24, 18:05:31 | 200 | |
| http://fneu.fr/distfiles/micro_proxy_30oct2002.tar.gz | 2013-05-24, 20:33:29 | 200 | |
| http://snow.critical.ch/distfiles/micro_proxy_30oct2002.tar.gz | 2013-05-25, 07:21:37 | 200 | |
| http://critical.ch/distfiles/micro_proxy_30oct2002.tar.gz | 2013-05-24, 17:37:22 | 200 | |
| ftp://ftp.c.saper.info/distfiles/micro_proxy_30oct2002.tar.gz | 2013-05-25, 00:57:49 | 200 | |
| http://energy.critical.ch/distfiles/micro_proxy_30oct2002.tar.gz | 2013-05-25, 05:52:12 | 200 |
