RE: obscure tomcat 5.5 text file display bug? [Bugzilla candidate?]

2005-07-06 Thread GB Developer
Indeed, thanks Jon. > -Original Message- > From: Woodchuck [mailto:[EMAIL PROTECTED] > Sent: Wednesday, July 06, 2005 10:15 AM > To: Tomcat Users List > Subject: Re: obscure tomcat 5.5 text file display bug? > [Bugzilla candidate?] > > > awesome!

Re: obscure tomcat 5.5 text file display bug? [Bugzilla candidate?]

2005-07-06 Thread Woodchuck
awesome! thanks, Jon! woodchuck --- Jon Wingfield <[EMAIL PROTECTED]> wrote: > I agree; it does the job :) > There is an equivalent for IE: > http://www.blunck.info/iehttpheaders.html > > Enjoy, > > Jon > > > Woodchuck wrote: > > > GB Developer, > > > > thanks so much for your suggestion,

RE: obscure tomcat 5.5 text file display bug? [Bugzilla candidate?]

2005-07-06 Thread Woodchuck
t; > Subject: RE: obscure tomcat 5.5 text file display bug? [Bugzilla > candidate?] > > > > here is the relevant header info from Tomcat 4.1: > > > > HTTP/1.x 200 OK > > Etag: W/"1706-1120587147968" > > Last-Modified: Tue, 05 Jul 2005 18:12:27 GM

Re: obscure tomcat 5.5 text file display bug? [Bugzilla candidate?]

2005-07-06 Thread Jon Wingfield
I agree; it does the job :) There is an equivalent for IE: http://www.blunck.info/iehttpheaders.html Enjoy, Jon Woodchuck wrote: GB Developer, thanks so much for your suggestion, Live HTTP Headers is awesome! and my hunch was correct. the problem is Tomcat 5.5 does not produce any Content

RE: obscure tomcat 5.5 text file display bug? [Bugzilla candidate?]

2005-07-05 Thread Caldarale, Charles R
> From: Woodchuck [mailto:[EMAIL PROTECTED] > Subject: RE: obscure tomcat 5.5 text file display bug? [Bugzilla candidate?] > > here is the relevant header info from Tomcat 4.1: > > HTTP/1.x 200 OK > Etag: W/"1706-1120587147968" > Last-Modified: Tue, 05 Jul 2005

RE: obscure tomcat 5.5 text file display bug? [Bugzilla candidate?]

2005-07-05 Thread Woodchuck
GB Developer, thanks so much for your suggestion, Live HTTP Headers is awesome! and my hunch was correct. the problem is Tomcat 5.5 does not produce any Content-Type information at all when serving back the .txt file. here is the relevant header info from Tomcat 4.1: HTTP/1.x 200 OK Etag: W/