| What about proxy authentication via LDAP? SSL options? Are these enabled by
| default?
|
| Along the lines of the PHP, Apache feature/module comparison tables (that
were
| posted earlier in this mailing list), it would be useful to see a feature
list
| of Squid comparing the other OS distri
Another point which I forgot to mention.
With the current layout (existing one), trying to create a sample module failed
with the following error.
-
% apxs -n foo -g
% cd foo
% make all reload
make: Warning: Can't find `/usr/
s.diff
Type: text/x-patch
Size: 1881 bytes
Desc: not available
URL:
<http://mail.opensolaris.org/pipermail/webstack-discuss/attachments/20070813/cd3c8d3e/attachment.bin>
Hi Rahul,
> The most often recommended options for squid compilation (along with
> some that is added for performance benefit)
>
>
> Options for SUNWsquid:
>
> --enable-async-io (Enable async IO with threa
As far as I poked around the source, these header files are not
actively used by any modules. So, it is okay , in my opinion, to simply
leave with the default MPM model.
thanks
sriram
Seema Alevoor wrote:
>> 1. I was wondering, for simplicity sake, should we not compile the
>> apache httpd i
The convention seems to be that build directory is found in the same
place / level where apache modules are kept. So, if we are going to
keep the modules under /usr/apache2/modules then the corresponding build
directory also needs to reside under /usr/apache2/build.
thanks
sriram
Seema Alevo