Sheth, Niraj writes:
> I also had the same problem, but withouth ssl.
>
> i could think of two solution.
> 1. Modify front end apache's source code manually( i guess default is
> HUGE_STRING_LEN (8k)), but it sounds little scary ..
>
> so i opted for second choice ...
>
> 2.
>
> i
Folks, thanks for all your immediate help. I think the problem is
clear now: I'm using a typical proxy setup with
lightweight SSL-frontends and heavyweight mod_perl-backends. What I
would like is an unbuffered output from the backends across the
frontends but the proxy setup is _buffering_:
Inte
Paul <[EMAIL PROTECTED]> wrote:
>
>--- darren chamberlain <[EMAIL PROTECTED]> wrote:
>> Dirk Lutzebaeck ([EMAIL PROTECTED]) said something to this effect:
>> > No, doesn't seem to matter in my case. Is there any place I can
>> verify
>> > that Apache has sent some data to the client?
>>
>> try:
>
--- darren chamberlain <[EMAIL PROTECTED]> wrote:
> Dirk Lutzebaeck ([EMAIL PROTECTED]) said something to this effect:
> > No, doesn't seem to matter in my case. Is there any place I can
> verify
> > that Apache has sent some data to the client?
>
> try:
>
> $ telnet myhost 80
> GET / HTTP/1.0
Dirk Lutzebaeck ([EMAIL PROTECTED]) said something to this effect:
> No, doesn't seem to matter in my case. Is there any place I can verify
> that Apache has sent some data to the client?
try:
$ telnet myhost 80
GET / HTTP/1.0
(two carriage returns)
You should see what the server is sending. F
Dirk Lutzebaeck <[EMAIL PROTECTED]> writes:
> Chip Turner writes:
> > You can always use the definitive test of tcpdump on the client
> > machine. Something like (on linux):
> >
> > /usr/sbin/tcpdump -s 4096 -w packets.out src (host) and port 80
> >
> > Then examine packets.out for what
Chip Turner writes:
> Dirk Lutzebaeck <[EMAIL PROTECTED]> writes:
>
> > > I've noticed that MSIE doesn't start displaying stuff until it has a certain
>amount,
> > > say a few hundred bytes. After that it displays just fine.
> >
> > No, doesn't seem to matter in my case. Is there any p
Dirk Lutzebaeck <[EMAIL PROTECTED]> writes:
> > I've noticed that MSIE doesn't start displaying stuff until it has a certain
>amount,
> > say a few hundred bytes. After that it displays just fine.
>
> No, doesn't seem to matter in my case. Is there any place I can verify
> that Apache has sen
Eric Cholet writes:
> > Steve van der Burg writes:
> > > >Hi, unbuffered output in a handler just doesn't work for me:
> > > [ details of setup and handler snipped ]
> > > >
> > > >If I 'GET /unbuffered' in Netscape nothing is printed until I stop the
> > > >server. Setting $|++ does no
> Steve van der Burg writes:
> > >Hi, unbuffered output in a handler just doesn't work for me:
> > [ details of setup and handler snipped ]
> > >
> > >If I 'GET /unbuffered' in Netscape nothing is printed until I stop the
> > >server. Setting $|++ does not help. Something is still buffering.
Steve van der Burg writes:
> >Hi, unbuffered output in a handler just doesn't work for me:
> [ details of setup and handler snipped ]
> >
> >If I 'GET /unbuffered' in Netscape nothing is printed until I stop the
> >server. Setting $|++ does not help. Something is still buffering. This
> >is
>Hi, unbuffered output in a handler just doesn't work for me:
[ details of setup and handler snipped ]
>
>If I 'GET /unbuffered' in Netscape nothing is printed until I stop the
>server. Setting $|++ does not help. Something is still buffering. This
>is modperl 1.21 and Apache 1.3.12.
>
>Any clues?
Hi, unbuffered output in a handler just doesn't work for me:
Options ExecCGI
SetHandler perl-script
PerlHandler My::Handler
package My::Handler;
sub handler {
my $r = shift;
$r->content_type('text/html');
$r->send_http_header;
while(1) {
$r->print("hi\n");
$r->rflush;
13 matches
Mail list logo
