Candidate Ignored Status - Revision history

84.161.158.127 at 13:47, 24 June 2007

2007-06-24T13:47:25Z

←Older revision		Revision as of 13:47, 24 June 2007


	These sources are marked as "ignored" instead of being deleted, because otherwise they could appear in the "DownloadMesh" of another host and be tried again, even though they have already been shown not to work.		These sources are marked as "ignored" instead of being deleted, because otherwise they could appear in the "DownloadMesh" of another host and be tried again, even though they have already been shown not to work.
		+
		+	[[Category:Documentation]]

84.161.158.127 at 13:44, 24 June 2007

2007-06-24T13:44:09Z

←Older revision		Revision as of 13:44, 24 June 2007

	* the candidate requires push, but I can't receive incomings.		* the candidate requires push, but I can't receive incomings.
	* the candidate requires push, but there is no valid push route.		* the candidate requires push, but there is no valid push route.
-	* the candidate uses chunked transfer encoding (Apache in certain cases)
	* the candidate returns 403 Forbidden, 404: File not found, or 410: Host not sharing		* the candidate returns 403 Forbidden, 404: File not found, or 410: Host not sharing
	* the HTTP protocol is not valid / can't be understood, failed to parse correctly.		* the HTTP protocol is not valid / can't be understood, failed to parse correctly.

84.161.158.127 at 13:43, 24 June 2007

2007-06-24T13:43:46Z

←Older revision		Revision as of 13:43, 24 June 2007

	Reasons for being marked ignored include:		Reasons for being marked ignored include:

-	* Phex failed to connect to the candidate 12 times in a row (min. ~27h).	+	* Phex failed to connect to the candidate 12 times in a row (min. ~27h).
-	* the candidate requires push, but I can't receive incomings.	+	* the candidate requires push, but I can't receive incomings.
-	* the candidate requires push, but there is no valid push route.	+	* the candidate requires push, but there is no valid push route.
-	* the candidate uses chunked transfer encoding (Apache in certain cases)	+	* the candidate uses chunked transfer encoding (Apache in certain cases)
-	* the candidate returns 403 Forbidden, 404: File not found, or 410: Host not sharing	+	* the candidate returns 403 Forbidden, 404: File not found, or 410: Host not sharing
-	* the HTTP protocol is not valid / can't be understood, failed to parse correctly.	+	* the HTTP protocol is not valid / can't be understood, failed to parse correctly.
-	* the candidate is banned or removed by the user.	+	* the candidate is banned or removed by the user.

	These sources are marked as "ignored" instead of being deleted, because otherwise they could appear in the "DownloadMesh" of another host and be tried again, even though they have already been shown not to work.		These sources are marked as "ignored" instead of being deleted, because otherwise they could appear in the "DownloadMesh" of another host and be tried again, even though they have already been shown not to work.

84.161.158.127 at 13:43, 24 June 2007

2007-06-24T13:43:29Z

New page

Sources are marked ignored, when Phex deems them no longer useful for anything.

Phex won't try to download from them again and they get deleted from the sources-list or a download when Phex quits.

Reasons for being marked ignored include:

* Phex failed to connect to the candidate 12 times in a row (min. ~27h).
* the candidate requires push, but I can't receive incomings.
* the candidate requires push, but there is no valid push route.
* the candidate uses chunked transfer encoding (Apache in certain cases)
* the candidate returns 403 Forbidden, 404: File not found, or 410: Host not sharing
* the HTTP protocol is not valid / can't be understood, failed to parse correctly.
* the candidate is banned or removed by the user.

These sources are marked as "ignored" instead of being deleted, because otherwise they could appear in the "DownloadMesh" of another host and be tried again, even though they have already been shown not to work.