Thanks Mike, for your reply. The way we have coded it, it already opens a socket, sends all the headers and the data (as much mentioned in the content-length header) and then closes the socket. If it needs to send more data, it opens another socket and goes through the same excercise. As it is, we very rarely will be doing multiple requests at any instance.
One interesting thing, I found out was, if I send the same message (with same headers and same data) to any port other than 80 (and 443), the proxy doesn't block it and am successfully able to see the activity at the server. So, I guess, the proxy is just filtering the messages on Port 80 (& 443). Also, the Remote HostIP at the server is different when I use port 80 to any other port. So, I guess the proxy is coming into play only when it thinks it is a HTTP(s) transaction. Thought, I would share this observation with you and may be, someone can come up with some ideas to help me out. Thanks, Kalyan "mike margerum" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > One thing I can tell you is even if you request a "keep-alive" status in > your http request, Sprint's cdma1x network will close your socket after > each request. You will see the "Connection: Close" in your http response > header. You have to create a new socket after each request. I never > could get an answer from them on why this is. i suppose it's some kind of > proxy issue. > -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
