Around position 319 of the http client wire trace. It happens on all computers in this school, but has not been observed in any of our other installations. It happens on all transactions with XML data greater than 319 characters.
I was able to patch by adding a 500 byte comment of known characters into the HTML and fixing up the data before it is parsed. Obviously not the best solution. I am pretty sure it is an environmental problem, but am not sure how to prove that. There are multiple security packages installed on the workstations. Do you know what processing takes place within java/http client before the http client wire trace is generated? Could this be a character encoding mismatch or something? -----Original Message----- From: Oleg Kalnichevski [mailto:[EMAIL PROTECTED] Sent: Thursday, October 04, 2007 3:58 AM To: HttpClient User Discussion Subject: Re: Transmission of XML with HttpClient 3-1 On Wed, 2007-10-03 at 11:42 -0400, Ken Richard wrote: > Hello. > > > > I have been using httpclient for a long time without any issues. Recently, > one of our installations has a problem where the XML coming back from the > server has a character being replaced with a \0. We ran a WireShark trace > and the data is correct, but the wire trace from httpclient shows the null. > The server for this transaction is Jetty. We are using the latest 3.1 jar > file. > > > > Here is an excerpt from my log. Note the /FIEL[0x0] on the last line. > > > > Has anyone seen this before? Do you have any recommendations? > Ken, Does this \0 appear randomly at different locations or at the same one? How reproducible is this problem? Oleg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
