Christopher Schultz-2 wrote:
>
> Try calling "flush" on your output stream, and possibly even closing it
> if you have to.
>
> Any reason not to use java.net.URLConnection for this?
>
No, reason. It was just very simple and sockets seemed to be appropriate.
--
View this message in context:
Say I have code like this:
protected void doPost( HttpServletRequest request, HttpServletResponse
response )
{
...
String requestString = "GET " + page + " HTTP/1.1";
String headersString =
"\r\nHost: " + request.getServerName() +
"\r\nCookie
