On Thu, Apr 29, 2004 at 03:05:34PM -0700, Dan Hollis wrote: > On Thu, 29 Apr 2004, seth vidal wrote: > > but something to relate that the problem is at the repo or in your > > connection to the repo and not just a problem with the world. > > what do you think? > > Just relaying the actual error message given to you directly by the server > seems most straightforward to me. Theres quite a lot of different codes > and instead of writing code to parse and handle them all, just pass on > what the server says. (obvious?) That _IS_ the error. The error is the lack of a content-length header. "no content-length returned". This usually suggests that you've hit dynamic content such as a directory listing. It's not a network error, but an indication that you're not getting what you think (an rpm or headers.info). -Michael -- Michael D. Stenner mstenner@xxxxxxxxxxxxxxx ECE Department, the University of Arizona 520-626-1619 1230 E. Speedway Blvd., Tucson, AZ 85721-0104 ECE 524G
