On Thu, 2006-11-23 at 15:40 +0100, Frode E. Moe wrote:
> On Thu, Nov 23, 2006 at 22:31:48 +0800, Dan Nelson wrote:
> > > Luckily, the 2.x version
> > > has been designed to support multiple protocols. See mod_echo (or
> > > mod_pop3 or mod_ftpd) for an exampl
On Thu, 2006-11-23 at 09:43 -0500, Joshua Slive wrote:
> > On Thu, 2006-11-23 at 09:18 -0500, Joshua Slive wrote:
> >
> > > But what you don't want is an HTTP server.
> >
> > True, although http would be suitable if I could reduce the
> unecessary
> > bandwidth from the headers.
>
> But the header
On Thu, 2006-11-23 at 09:18 -0500, Joshua Slive wrote:
> But what you don't want is an HTTP server.
True, although http would be suitable if I could reduce the unecessary
bandwidth from the headers.
> Luckily, the 2.x version
> has been designed to support multiple protocols. See mod_echo (or
On Thu, 2006-11-23 at 11:21 +, Nick Kew wrote:
> No headers at all?
I'd like to get rid of as many as I can. But I can't seem to get rid of
any, well, except the ones I create myself.
> You can't do that in response to an HTTP/1.x
> request, because (bugs aside), Apache won't break HTTP a
On Thu, 2006-11-23 at 11:32 +0100, Matus UHLAR - fantomas wrote:
> Why do you want to use apache (HTTP server) when you want your application
> send no headers (e.g. no HTTP response)?
Because Apache is robust, efficient, flexible, bulletproof, easy to
interface to virtually any database, easy to
I'm running Apache 2.0 on Debian Sarge.
I have a non-standard application for Apache, and don't want to send any
headers in the response. I thought I'd be able to do so using
mod_headers.
I can use the 'Header' directive to add my own header, and then append
to and unset it. But using the same
