Hello Daniel, > com.firstam.rets.exception.RETSException: > org.apache.commons.httpclient.ProtocolException: The server > xxx.xxx.xxx.com failed to respond with a valid HTTP response
Please post a wire log, so we know what the HTTP server responds. http://jakarta.apache.org/commons/httpclient/logging.html Feel free to hide host names and passwords in the log. But you should make sure to hide all occurrences and not just the first one ;-) > Caused by: org.apache.commons.httpclient.ProtocolException: The server > [...].com failed to respond with a valid HTTP response That query string you are using is bad. You really should switch to a POST or PUT request and send the parameters in the message body. That's what it's there for. RFC 2616 has a few words to say on URL length, for example in 3.2.1: The HTTP protocol does not place any a priori limit on the length of a URI. Servers MUST be able to handle the URI of any resource they serve, and SHOULD be able to handle URIs of unbounded length if they provide GET-based forms that could generate such URIs. A server SHOULD return 414 (Request-URI Too Long) status if a URI is longer than the server can handle (see section 10.4.15). Note: Servers ought to be cautious about depending on URI lengths above 255 bytes, because some older client or proxy implementations might not properly support these lengths. cheers, Roland --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
