Vincent Veyron wrote:
No you don't. If in one Apache you say
Listen 80
Listen 443
and it will listen to both ports.
That I didn't know. I will try it, thanks
..
(but only once, for HTTPS; the reason for that is longer to explain).
Well, if I'm not mistaken it's simply because the request
> No you don't. If in one Apache you say
> Listen 80
> Listen 443
>
> and it will listen to both ports.
That I didn't know. I will try it, thanks
> ..
>
> (but only once, for HTTPS; the reason for that is longer to explain).
>
Well, if I'm not mistaken it's simply because the request being c
On Tue, Sep 21, 2010 at 4:57 PM, Vincent Veyron wrote:
> I realized after the fact that updates _are_ a problem. I suppose one
> has to recompile from source. I'm hoping to script the process,
> eventually.
Off-topic: will gentoo ports work with debian? "emerge mod_perl" ==
"script the process"
Hello, I'm currently attempting to update an Apache Cluster from Apache 1.3
to Apache2. The Cluster is running Debian (Lenny). The website served by
this cluster uses Template Toolkit extensively. A link to template toolkits
home page:
http://template-toolkit.org/
Sitting in-between Apache2
Btw, if you simply want to disable chunked encoding, buffer your output in
your mod_perl handler, set the Content-Length response header once your
output is complete and only after that print your output.
Apache only activates chunked encoding if no Content-Length header is
present when output is
Hi,
your problem has nothing to do with the mod_perl output. The 20d and 0 are
length descriptors for chunked encoding, check out the response header:
Transfer-Encoding: chunked
This SHOULD be supported by a HTTP 1.1 client. In fact, I would be
surprised if cadaver/neon couldnt handle this.
Wha
