2013/12/7 Christopher Schultz :
> On 12/6/13, 1:07 PM, Mark Thomas wrote:
>> On 06/12/2013 17:33, C. Benson Manica wrote:
>>> I'm sure it *is* some kind of buffer boundary - 16384 is not a
>>> random number ;-) As it happens, I *did* miss some logging (my
>>> IDE made it easy to miss). I have no id
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Mark,
On 12/6/13, 1:07 PM, Mark Thomas wrote:
> On 06/12/2013 17:33, C. Benson Manica wrote:
>> I'm sure it *is* some kind of buffer boundary - 16384 is not a
>> random number ;-) As it happens, I *did* miss some logging (my
>> IDE made it easy to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
C.,
On 12/5/13, 8:06 PM, C. Benson Manica wrote:
>> I got this back: (apologies if the fixed-width formatting doesn't
>> come through)
It came through just fine.
>> 16:34:44.954734 IP6 localhost.http-alt > localhost.61592: Flags
>> [P.], seq 1:900
On 06/12/2013 17:33, C. Benson Manica wrote:
> I'm sure it *is* some kind of buffer boundary - 16384 is not a
> random number ;-) As it happens, I *did* miss some logging (my IDE
> made it easy to miss). I have no idea what this exception means
> though:
>
> SEVERE: Servlet.service() for servlet [
I'm sure it *is* some kind of buffer boundary - 16384 is not a random
number ;-) As it happens, I *did* miss some logging (my IDE made it easy to
miss). I have no idea what this exception means though:
SEVERE: Servlet.service() for servlet [jsp] in context with path [] threw
exception [java.lang.A
"C. Benson Manica" schrieb:
>On Thu, Dec 5, 2013 at 10:58 AM, Christopher Schultz <
>ch...@christopherschultz.net> wrote:
>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA256
>>
>> C.,
>>
>> On 12/5/13, 12:53 PM, C. Benson Manica wrote:
>> > The content I expect is in the neighborhood of 30
On Thu, Dec 5, 2013 at 10:58 AM, Christopher Schultz <
ch...@christopherschultz.net> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> C.,
>
> On 12/5/13, 12:53 PM, C. Benson Manica wrote:
> > The content I expect is in the neighborhood of 30K. What I get back
> > is
> >
> > $ curl -i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
C.,
On 12/5/13, 12:53 PM, C. Benson Manica wrote:
> The content I expect is in the neighborhood of 30K. What I get back
> is
>
> $ curl -i http://localhost:8080/
>
> HTTP/1.1 200 OK^M Server: Apache-Coyote/1.1^M Set-Cookie:
> JSESSIONID=6ED488F581
Hi,
> -Original Message-
> From: C. Benson Manica [mailto:cbman...@gmail.com]
> Sent: Thursday, December 5, 2013 6:54 PM
> To: Tomcat Users List
> Subject: Re: Transfer-Encoding: chunked not working
>
> The content I expect is in the neighborhood of 30K. What I get b
The content I expect is in the neighborhood of 30K. What I get back is
$ curl -i http://localhost:8080/
HTTP/1.1 200 OK^M
Server: Apache-Coyote/1.1^M
Set-Cookie: JSESSIONID=6ED488F581B8D3317261ADA2AD97CC20; Path=/; HttpOnly^M
Content-Type: text/html;charset=UTF-8^M
Transfer-Encoding: chunked^M
Da
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Benson,
On 12/3/13, 6:55 PM, C. Benson Manica wrote:
> Tomcat 7.0.47, OSX 10.8. Fresh install via homebrew.
[As an aside, I'm interested in your experience with
Tomcat-via-homebrew. I use Mac OS but installed Tomcat via
direct-download. Does brew m
Also, if HTTP 1.1 weren't enabled for some reason, wouldn't the default
simply be to serve the entire content, rather than the first 16384 bytes?
On Tue, Dec 3, 2013 at 4:44 PM, C. Benson Manica wrote:
> connectionTimeout="2"
>redirectPort="8443" />
>
> sure
sure looks like 1.1 to me.
On Tue, Dec 3, 2013 at 4:38 PM, Martin Gainty wrote:
> chunked only works on HTTP 1.1 connections
> display $CATALINA_HOME/conf/server.xml
>
> Martin--
>
>
>
>
>
> > Date: Tue, 3 Dec 2013 15:55:22 -0800
> > Subject: Transfer-Encoding: chunked not working
> > From: c
chunked only works on HTTP 1.1 connections
display $CATALINA_HOME/conf/server.xml
Martin--
> Date: Tue, 3 Dec 2013 15:55:22 -0800
> Subject: Transfer-Encoding: chunked not working
> From: cbman...@gmail.com
> To: users@tomcat.apache.org
>
> Tomcat 7.0.47, OSX 10.8. Fresh install via homeb
14 matches
Mail list logo