On Mar 31, 2008, at 13:31, Paul Querna wrote:
Just look at SSLRequire, Rewrite*, MPM Process/Thread Management,
Filter chaining, large Auth{N,Z} chains, and more.
Imagine them not sucking.
That would be lovely. Truly.
--
Happiness isn't something you experience; it's something you
On Mar 31, 2008, at 13:46, Issac Goldstand wrote:
Make mod_wombat a standard module and part of the default moduleset
May I request, if mod_wombat becomes a standard module, that it be
given a name not quite so calculated to make the newbie disable it
without a second glance. I mean,
On 4/2/08 8:44 AM, Rich Bowen [EMAIL PROTECTED] wrote:
May I request, if mod_wombat becomes a standard module, that it be given a
name not quite so calculated to make the newbie disable it without a second
glance.
I think the reason wombat was chosen is because mod_lua was taken. In
There's a couple of conflicting demands by our users, and spending
time on the users mailing list and on the IRC channel is a great way
to see this first-hand.
They don't want to learn a new syntax. And they want a new syntax
that lets them do what they mean.
And they're very frustrated
Issac Goldstand wrote:
We're not talking about fresh users, we're talking about existing
users. Fresh users have to deal with one learning curve or another
anyway.
I'm not talking about fresh users either.
Matt
Akins, Brian wrote:
The biggest problems I have with current system are:
-Every module does things differently
Within limits this will remain true. But we are missing a host of very
trivial simplifications for the casual module developer, and reinvent the
same wheel module after module.
I'm
Graham Leggett wrote:
Jim Jagielski wrote:
This reminds me: a serf BOF or session would, I think, go over
quite well :)
A question that has been on my mind for a bit, is what does serf intend
to replace, and why is it better?.
The impression I have so far is that somehow what we have now
William A. Rowe, Jr. wrote:
-I have to write a good bit of code before a module is configurable. (I'm
lazy. Very lazy.)
Agreed - see my first point.
One interesting point; why do we keep per-server and per-dir sections?
Perhaps it's time for a single simpler-to-use mechanic which can
William A. Rowe, Jr. wrote:
William A. Rowe, Jr. wrote:
-I have to write a good bit of code before a module is configurable.
(I'm
lazy. Very lazy.)
Agreed - see my first point.
One interesting point; why do we keep per-server and per-dir sections?
Perhaps it's time for a single
Ahem,
On that subject, libapreq1 is already a year and a half into it's latest
release cycle. We're still waiting for a PMC vote to finish the
release... Someone remind me to do a lightning talk about this next
time I'm at AC :)
Foo JH wrote:
Fantastic! Can I assume that libapreq will
Issac Goldstand wrote:
Ahem,
On that subject, libapreq1 is already a year and a half into it's latest
release cycle. We're still waiting for a PMC vote to finish the
release... Someone remind me to do a lightning talk about this next
time I'm at AC :)
Time for a FFT presentation - 15
William A. Rowe, Jr. wrote:
Issac Goldstand wrote:
Ahem,
On that subject, libapreq1 is already a year and a half into it's
latest release cycle. We're still waiting for a PMC vote to finish
the release... Someone remind me to do a lightning talk about this
next time I'm at AC :)
Time
On 03/04/2008, Olexandr Prokhorenko [EMAIL PROTECTED] wrote:
Hi everyone,
I am working on the input filter which is going to catch on input requests,
find the bucket with Host: , modify it and pass it through. I will modify
it to something that does not belong to my httpd server, so I
This technique is taken from modules/proxy/mod_proxy.c in Apache
source code. See the proxy_detect() function in that file for a C code
example.
One could change request headers on way through in same handler
function as setup the proxy. Still need an output filter if you want
to change handlers
14 matches
Mail list logo
