On Thu, Apr 29, 2004 at 06:00:20PM -0400, seth vidal wrote: > > This particular error message has been discussed many many times. > > It's going away, so lets not get into it in great detail. The problem > > is that the code must be cross-protocol and there is not alway a > > useful error message to report. That particular check covers MANY > > problems and it is not always possible to know precisely which of them > > is happening. > > You know - it might be useful to say something just a bit more specific. > > Like: > something is wrong with: > your connection > the server > your worldview > your politics > etc. > > ok so just the first two, really. > 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? Hell, I think that's a great idea. The most common causes of that error are a screwy configuration or a screwy server. It's not usually a connection issue. Perhaps "No Content-Length returned - check the url" or similar. -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
