The [0x0] values are just a product of the Wire log. It interprets the logged values as ASCII and treats all non printing ASCII values in this way. [0x0] corresponds to the ASCII value 0.

Mike

Zulfi Umrani wrote:
Instead of caching HttpClient, I cached HttpState and it worked fine.
Now, how can I not send trailing [0x0] after each HTTP body?

Thanks.


[EMAIL PROTECTED] 6/27/2003 2:23:45 PM >>>

Zulfi,


First of all, Tomcat 4.0.4 can be considered fairly out-dated and is
known to have a few bugs. Do consider upgrading.

My guess is that the version of Tomcat you are running is having
issues
with RFC2109 formatted cookies. Try using compatibility cookie policy
and see if it has any effect. Besides, you may want to examine Tomcat
logs for clues as to why it does not like the cookie

Oleg

On Fri, 2003-06-27 at 17:10, Zulfi Umrani wrote:

I hung on to the HttpClient instance and seems like it is sending
cookies now. But it still did not work successfully, because Apache
Tomcat Server is returning a wiered message. When I do not send

cookies,


it accepts the POST request. But as soon as cookie is sent, it sends
back 501! Attached is the wire log. I have canged the body of  HTTP
because of confidentiality. I also see whole bunch of [0x0]s being

added


at the end of each body. Is there any way not to send them? Could

they


be the cause of the problem?
I will appreciate a response.

Thanks.




---------------------------------------------------------------------
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]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to