Re: Header lines appearing in body after redirect with IIS.

2001-04-05 Thread Guntupalli Shanti

Hi Jacob,

I had the same problem...but only with IE, with Netscape it was fine.
In my case, the connection was kept alive and the output is
appended to the response buffer whenever I use sendRedirect method.
I added the following line to my code before reading anything
from response object (best place would be at the beginning of the Service 
method).

response.setHeader("Connection","close")

I don't know if this is of any help in your case as the Connection appears 
to be closed
from the Headers you have given

Cheers,
Shanti

At 02:40 PM 4/5/2001 -0400, you wrote:
Hi,

After I changed to using IIS instead of Tomcat's built-in web server, I
encountered the following problem:

I request a web page that redirects to a second web page after writing some
output.  The resulting web page contains this initial output plus the
following header fields plus the web page that I was redirected to:

HTTP/1.1 200 OK
Server: Microsoft-IIS/4.0
Date: Thu, 05 Apr 2001 18:19:38 GMT
Connection: close
Content-Type:text/html
Pragma:no-cache
Cache-Control:no-cache
Expires:Thu, 01 Jan 1970 00:00:00 GMT
Servlet-Engine:Tomcat Web Server/3.2.1 (JSP 1.1; Servlet 2.2; Java 1.2.2;
Windows NT 4.0 x86; java.vendor=Sun Microsystems Inc.)


I know that I can't write output before redirecting, but the output should
have stayed in the buffer and then been cleared when I tried to redirect.
This is what appears to be happening with Tomcat's built-in web server, in
which case everything appears to be ok.  In any case, I think I would have
gotten an error if I had sent the output back to the client before
redirecting.  I tried setting the %@page buffer="64k"% (or "64kb"), but
this didn't do anything and I know that I didn't have 64k of text in the
buffer.

Has anyone else encountered anything similar to this?

Thank you for any help.


Jacob Shukert
[EMAIL PROTECTED]
(703) 341-2751, VNET 235-2751
Source Systems Development
MCI WorldCom




RE: Header lines appearing in body after redirect with IIS.

2001-04-05 Thread Jacob Shukert

Hi Shanti,

That worked!  Thank you very much.

Jacob Shukert
[EMAIL PROTECTED]
(703) 341-2751, VNET 235-2751
Source Systems Development
MCI WorldCom

-Original Message-
From: Guntupalli Shanti [mailto:[EMAIL PROTECTED]]
Sent: Thursday, April 05, 2001 2:56 PM
To: [EMAIL PROTECTED]
Subject: Re: Header lines appearing in body after redirect with IIS.


Hi Jacob,

I had the same problem...but only with IE, with Netscape it was fine.
In my case, the connection was kept alive and the output is
appended to the response buffer whenever I use sendRedirect method.
I added the following line to my code before reading anything
from response object (best place would be at the beginning of the Service
method).

response.setHeader("Connection","close")

I don't know if this is of any help in your case as the Connection appears
to be closed
from the Headers you have given

Cheers,
Shanti

At 02:40 PM 4/5/2001 -0400, you wrote:
Hi,

After I changed to using IIS instead of Tomcat's built-in web server, I
encountered the following problem:

I request a web page that redirects to a second web page after writing some
output.  The resulting web page contains this initial output plus the
following header fields plus the web page that I was redirected to:

HTTP/1.1 200 OK
Server: Microsoft-IIS/4.0
Date: Thu, 05 Apr 2001 18:19:38 GMT
Connection: close
Content-Type:text/html
Pragma:no-cache
Cache-Control:no-cache
Expires:Thu, 01 Jan 1970 00:00:00 GMT
Servlet-Engine:Tomcat Web Server/3.2.1 (JSP 1.1; Servlet 2.2; Java 1.2.2;
Windows NT 4.0 x86; java.vendor=Sun Microsystems Inc.)


I know that I can't write output before redirecting, but the output should
have stayed in the buffer and then been cleared when I tried to redirect.
This is what appears to be happening with Tomcat's built-in web server, in
which case everything appears to be ok.  In any case, I think I would have
gotten an error if I had sent the output back to the client before
redirecting.  I tried setting the %@page buffer="64k"% (or "64kb"), but
this didn't do anything and I know that I didn't have 64k of text in the
buffer.

Has anyone else encountered anything similar to this?

Thank you for any help.


Jacob Shukert
[EMAIL PROTECTED]
(703) 341-2751, VNET 235-2751
Source Systems Development
MCI WorldCom