DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9129>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9129 <url> condition considers a 404 error OK Summary: <url> condition considers a 404 error OK Product: Ant Version: 1.5Beta1 Platform: Other OS/Version: Windows XP Status: NEW Severity: Normal Priority: Other Component: Core tasks AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] So the <condition>/<waitfor> test spins against a URL waiting for it to come back, right? But a 404 response, "not found" is an error in my opinion; the task should spin for 30s until that condition goes away or something. Succeeding on a 4xx response is incorrect behaviour, IMO options 1. move the bar down so that only reponses below 400 are accepted 2. provide some means to override the current value (a minvalue and maxvalue?) -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
