rms. See the mod_ssl INSTALL document for details on
< how to build Apache+EAPI with shared memory support.
---
> platforms.
vh
Mads Toftum
--
`Darn it, who spiked my coffee with water?!' - lwall
-
To
ed by mod_ssl for
various reasons. So the actually allocated shared memory is always
1MB more than what you specify on SSLSessionCache.
vh
Mads Toftum
--
`Darn it, who spiked my coffee with water?!' - lwall
-
To unsu
d_ssl. On platforms where you use GCC/GDB you have to
build
+Apache. On platforms where you use GCC/GDB you have to build
Apache+mod_ssl with ``OPTIM="-g -ggdb3"'' to achieve
this. On
other platforms at least ``OPTIM="-g"'' is neede
ion. That section can then be used as a base for the
page once 2.2 is released. For the individual directives the Compatibility
section should be fine.
vh
Mads Toftum
--
`Darn it, who spiked my coffee with water?!' - lwall
ese HTML files contain nasty messages to anyone who would care to try
> to provide us with patches.
>
+1.
As it is I'd much prefer to have xml only for all generated pages in cvs
and only create html when rolling the tarball.
vh
Mads Toftum
--
`Darn it, who spiked my coffee with water?!' - lwall
we could use separate directories for xml and html, like the
> httpd-site does. I would support that.
>
Yes, definetely +1. It will make it easier to distribute binaries
without the xml and look much cleaner.
vh
Mads Toftum
--
`Darn it, who spiked my coffee with water?!' - lwall
- take f.ex. the mod_rewrite page, sorting the list
of directives leaves the most important and most often used directive
(RewriteRule) at the end of the file, making it the last thing you see.
vh
Mads Toftum
--
`Darn it, who spiked my coffee with water?!' - lwall
---
beat me to it. I was trying to clear up a problem with my commit
mail not reaching the cvs list without having someone approve it.
vh
Mads Toftum
--
`Darn it, who spiked my coffee with water?!' - lwall
-
To unsubscribe, e-m
direct this type of question to the users
list: http://httpd.apache.org/lists.html#http-users
vh
Mads Toftum
--
`Darn it, who spiked my coffee with water?!' - lwall
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For ad
of misinformation. I think we've discussed this one into the ground, and
> I think we were in agreement that it's not a wonderful idea. Perhaps it
> should get taken out of the STATUS file.
>
Yeah, let's kill this one.
vh
Mads Toftum
--
`Darn it, w
less on the docs side (unless someone feels like making and english only
version ;)
vh
Mads Toftum
--
`Darn it, who spiked my coffee with water?!' - lwall
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
a pain. A less radical approach could be to have the
base version with english only and then an optional language pack containing
all others.
Personally I like what we have now. Being able to read the docs without
a running Apache would be a plus, but that's about the only
#vhosts2
http://httpd.apache.org/docs-2.0/ssl/ssl_faq.html#vhosts
vh
Mads Toftum
--
`Darn it, who spiked my coffee with water?!' - lwall
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
t; *.foo.com, you build Virttualhosts a.foo.com, etc.).
>
Which unfortunately isn't very portable - different ways work with different
browsers etc. We've had this discussion more than once on modssl-users -
check back in the archive for details.
vh
Mads Toftum
--
`Darn it, who sp
d seperately from
www.modssl.org and thus not really something we should write too much
about in the docs imho.
vh
Mads Toftum
--
`Darn it, who spiked my coffee with water?!' - lwall
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
F
ier to understand (at least
that's why I added it).
vh
Mads Toftum
--
`Darn it, who spiked my coffee with water?!' - lwall
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
have any exact figures for this, but it does appear to me (looking
at local rbl stats) that open proxies are becoming much more popular
among spammers than the old open relays.
vh
Mads Toftum
--
`Darn it, who spiked my coffee with water?!' - lwall
-
make it so, but there could still be bigger
changes even in 2.0.x and definetely in 2.1.x.
Should it say something about 3rd party modules?
vh
Mads Toftum
--
`Darn it, who spiked my coffee with water?!' - lwall
-
To uns
in my
other projects as a convenience.
vh
Mads Toftum
--
`Darn it, who spiked my coffee with water?!' - lwall
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
e new_features and
upgrading docs in 2.1. They look like the ones in 2.0.
vh
Mads Toftum
--
Speaking at ApacheCon 2003 - http://ApacheCon.com/
T03, "Apache 2 mod_ssl tutorial" (3h)
WE03, "Troubleshooting Apache configurations"
WE11, "Apache
On Mon, Jan 26, 2004 at 02:06:06PM +0100, André Malo wrote:
[SNIP lots of good points]
>
> all IMHO, of course.
>
agreed - that's roughly my conclusion after looking at Doco.
There's no sense in undoing all the hard work that has
already been done.
vh
Mads Toftum
--
`Dar
Word swap files? Pico swap
> files?
>
We already have IndexIgnore .??* *~ *# HEADER* README* RCS CVS *,v *,t
Maybe that is a good measure of files you probably don't want to
serve?
If we don't put it in the default conf, then we should at least put
it in the security doc.
vh
On Tue, Feb 17, 2004 at 11:24:06AM +0100, Sascha Kersken wrote:
> In LDAPCacheEntries - Description:
>
> "Maximum number of entires in the primary LDAP cache"
>
> entires -> entries
>
Fixed, thanks for spotting this.
vh
Mads Toftum
--
`Darn it, who spiked
ut for a couple of years now.
Spare time is not something I've had too much of lately, but I'd
certainly want to give a hand with the mod_rewrite docs and I suppose
some of the examples from my mod_rewrite talk could be useful.
vh
Mads Toftum
--
`Darn it, who spiked my coffee with
round to sending it :)
> You can update your bookmarks according.
>
> ... Another option would also be, add a checkbox for a doc cookie,
> 'Always choose this version', which would bypass this page and
> always redirect that browser to the right section.
>
A nice added
er version. If we go with this, I'll hack together a script to let
translators know which pages that needs translating.
vh
Mads Toftum
--
`Darn it, who spiked my coffee with water?!' - lwall
-
To unsubscribe, e-mail: [EMAIL
#x27;t had the time to read the archive yet).
vh
Mads Toftum
--
`Darn it, who spiked my coffee with water?!' - lwall
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
On Mon, Nov 29, 2004 at 01:10:00PM +0100, André Malo wrote:
> (And when I see the output of the forrest using projects, I don't like it).
>
+1. Both for the looks and for not liking the idea of running the site
on cocoon.
vh
Mads Toftum
--
`Darn it, who spiked my coffee with water
invalidate the
> translation, a normal page would get a warning (like the docs).
>
That sounds like a very good solution to me.
vh
Mads Toftum
--
`Darn it, who spiked my coffee with water?!' - lwall
-
To un
and actually get it done
> before yet another year passes on this conversation.
>
+1 - I have a few cycles to spend on this in the next couple of months
and I have some potentially useful content from my apachecon talks.
vh
Mads Toftum
--
`Darn it, who spiked my coffee with water?!'
be available with CVS) and just import the latest docs
> into the 1.3 branch. -- justin
+1. I don't see a problem with that, as long as we don't see any of the
original docs history from the time before the docs were moved away.
vh
Mads Toftum
--
`Darn it, who spi
On Wed, Jan 05, 2005 at 04:51:37PM -0500, Rich Bowen wrote:
> I don't see any particular problem with losing the docs history. It's
> not nearly as important in the docs as it is elsewhere.
>
And it isn't even entirely lost, just requires a bit of extra archeology
to dig
> provide it from our own servers.
>
Agreed again. I certainly don't think we should rely on someone else to
generate new versions.
vh
Mads Toftum
--
`Darn it, who spiked my coffee with water?!' - lwall
-
To
account needs to be reenabled. I'll pass on your
message so that the account can be reopened.
vh
Mads Toftum
--
`Darn it, who spiked my coffee with water?!' - lwall
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
Fo
be? I see no
> reason to turn off indexes either. But I don't care if it's turned off ;)
>
+1
vh
Mads Toftum
--
`Darn it, who spiked my coffee with water?!' - lwall
-
To unsubscribe, e-mail: [EMAI
ache what
> is logged and what isn't?
> Cheers for any help in advance!
>
Docs is not a user help list - you want
http://httpd.apache.org/lists.html#http-users
There's also the documentation at
http://httpd.apache.org/docs-2.0/mod/mod_log_config.html and
http://httpd.apache.org/
; to be something that I actually want to do.
>
It is all a question of what type of dbm mod_rewrite uses - just
choosing the one you find most convenient isn't going to work.
vh
Mads Toftum
--
`Darn it, who spiked m
l
performace killer. AFAIK ajax is more than busy enough as it is, it
doesn't need more to do. If you really want to go through with this,
then make it a lot simpler to get rid of the -d and -f.
vh
Mads Toftum
--
`Darn it, who spiked my coffee with water?!' - lwall
--
;
> RewriteCond ${dir2url:${tolower:$1}} (.+)
> RewriteRule ^/+docs/+([^/]+)$ /docs/2.0/%1 [R=301,NE,L]
>
Much better.
> I'm not sure how and when to convert to dbm, though (possibly
> automatically). Ideas?
>
httxt2dbm? Maybe the txt file could be generated when generating the
hing on the serverside,
so all we need is to convince someone with access to set up a cronjob to
do the actual conversion.
vh
Mads Toftum
--
`Darn it, who spiked my coffee with water?!' - lwall
-
To unsubscribe, e-mail: [EMAIL
d really hate to start a build of all languages by accident
- it takes forever and I've seen problems with the encodings at one
point.
vh
Mads Toftum
--
`Darn it, who spiked my coffee with water?!' - lwall
-
To uns
thus a bit of extra
> paranoia for good measure :-)
>
That's what the rest of us use umask for.
vh
Mads Toftum
--
`Darn it, who spiked my coffee with water?!' - lwall
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
On Sun, Oct 30, 2005 at 12:19:00PM +, Joe Orton wrote:
> On Sun, Oct 30, 2005 at 05:38:40AM -0500, Jeff Trawick wrote:
> > Does anybody consider that program useful? (doc it or yank it?)
>
> No, I vote yank.
>
Agreed. I wonder if sticking that test in httpd -t would be w
have been talking about redoing the mod_rewrite docs for
years, but never got around to much more than talking, and I imagine
that Rich might have a bit of a problem doing much with them now...
http://wooga.drbacchus.com/wordpress/?p=1176
vh
Mads Toftum
--
`Darn it, who spiked my coffee with
more, using more space and slowing things down. For those
who don't care enough about logging to change it, the minimal format is
probably the best choice.
That being said, shouldn't this discussion be on [EMAIL PROTECTED]
vh
Mads Toftum
--
`Darn it, who s
the case, perhaps this
> isn't worth pursuing. I was just thinking "out loud."
>
Nothing major, but it will still grow the logs by quite a bit.
vh
Mads Toftum
--
`Darn it, who spiked my coffee with water?!' - lwall
-
ink it is going to be a whole lot more trouble than it is worth -
but as long as you don't get wiki diffs mailed to this list, I suppose
it will be easy enough to ignore ;)
vh
Mads Toftum
--
`Darn it, who spiked my coffee with water?!' - lwall
---
ave it to someone else to generate
>the HTML?
>
That does happen at times when people have trouble generating the html,
but with Andre not going through and picking up everyone elses mess as
often as he used to, that isn't fabulous.
vh
docs link to this article, so it must be true) was
> unfortunate, and undesirable.
>
+1 - I don't think a single users abuse should force us into making a
catch all policy. Part of the price of running a wiki is that you'll
have to deal with abuse from time to time.
vh
Mads T
_rewrite is difficult to grasp and
tricking them into thinking that it isn't won't help one bit.
As it is, someone else has already stripped more than enough of the
original warnings and I'd be +1 to keeping the ones that are still there
today.
vh
Mads Toftum
--
http://soulfood
- we've got something very useful inside
the httpd docs, let's not dump it.
vh
Mads Toftum
--
http://soulfood.dk
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
, Mads, can you explain how you see these docs evolving?
>
I'm not going to get into a long rant about why I don't like wikis - one
only has to review the recent thread here to see why...
That being said, if something useful evolves in the wiki, I'm all for
pulling it back into
be fully in favor of deleting the rewriteguide in the main docs
> and linking to the wiki.
>
In that case, please give me a bit of time to copy things over if it
ever gets that far - I'd rather do that than see the wiki take over as
the authoritative doc.
vh
Mads T
t; enough to commit changes to xdocs, do an svn update on people.apache.org
> and ant will be run there?
>
xdocs needs to be run locally and both the xml and resulting html has to
be committed - at least that's how it is done with the httpd docs.
vh
Mads Toftum
iciently with our structured documentation.
> Regarding Google, who's making the money from the searches? I came
I'm not too worried about the $$, but given the amount of competition
among the search engines out there, choosing si
gt; previously documented)" per document, for clarification.
>
Very bad idea IMHO - reverse proxy is widely used and gateway is often
used when you're describing outgoing connections, not incomming.
vh
Mads Toftum
--
http://soulfood.dk
---
t; anymore (as we did with the old license header [1]) I think we're
> good with updating it now...
>
Agreed, +1.
vh
Mads Toftum
--
http://soulfood.dk
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
forth in wikis, I
have no clue, I still think wikis are a bad idea - we obviously don't
get much in the way of reviews there.
vh
Mads Toftum
--
http://soulfood.dk
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
menu bar
> and horizontal rules in the new design, and am absolutely -1 on any change
> to our project logo (which is different from the ASF logo).
>
Agreed. I'd really hate to have the docs messed up by the new design.
Readablity should take preference over fancy new colors.
vh
Mads T
es). Adapting the front page to the standard of
> the docs would seem a better goal.
>
Agreed. +1
vh
Mads Toftum
--
http://soulfood.dk
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
erences as it is.
Keeping it to major versions might help reduce the confusion.
vh
Mads Toftum
--
http://soulfood.dk
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
confusion.
I think modules.apache.org would be a more suitable place for such info.
vh
Mads Toftum
--
http://soulfood.dk
-
To unsubscribe, e-mail: docs-unsubscr...@httpd.apache.org
For additional commands, e-mail: docs-h...@httpd.apache.org
at mod_rewrite is capable of and I'd be happy to dig them out and add
them to the docs if that'd be any help.
Should we just go ahead and make a "when not to use mod_rewrite guide"?
vh
Mads Toftum
--
http://soulfood.dk
-
lit could be:
1. redirecting/remapping
2. controlling access
3. when not to use mod_rewrite (see my response to Nick)
3. advanced features
vh
Mads Toftum
--
http://soulfood.dk
-
To unsubscribe, e-mail: docs-unsubscr...@httpd.apache.or
primary interest is 2.2 and older - while interesting, I don't think
trunk is worth too much effort just yet ;)
vh
Mads Toftum
--
http://soulfood.dk
-
To unsubscribe, e-mail: docs-unsubscr...@httpd.apache.org
ent.
>
> Perhaps 2) but give examples of usage for popular/confusing ones elsewhere?
>
+1 - I don't mind reference docs with good examples, but the opposite is
not a good thing.
vh
Mads Toftum
--
http://soulfood.dk
-
T
to get rid of the whole page.
If not, most of it probably needs to be rewritten to compare to slightly
more recent things.
The only thing that seems useful to me is the Custom Log Functions section.
vh
Mads Toftum
--
http://soulfood.dk
---
"comp.infosystems.www.servers.ms-windows" (as appropriate for the platform
> you use)."
>
> Are these active, useful and clueful still?
>
I can't speak for the windoze group, but the unix one is better than
most newsgroups these days. Perhaps not the most a
e much in favor of
leaving the 1.3 docs online for, ehrm, "historical reference".
vh
Mads Toftum
--
http://soulfood.dk
-
To unsubscribe, e-mail: docs-unsubscr...@httpd.apache.org
For additional commands, e-mail: docs-h...@httpd.apache.org
On Tue, Mar 29, 2011 at 12:13:39PM +0100, Vincent Bray wrote:
> Why not just link to here? http://httpd.apache.org/contributors/
>
That doesn't seem to be completely in sync either.
vh
Mads Toftum
--
http://soulfood.dk
-
and simple way to handle it would be steali^Wborrowing the code
that generates http://projects.apache.org/ Having people submit their
modules with DOAP files would probably make it very close to 0 code
effort.
vh
Mads Toftum
--
http://soulfood.dk
te-tools/trunk/projects/
Really it'd just be some minor tweaking of the tamplates and figuring
out a different pickup other than files.xml.
vh
Mads Toftum
--
http://soulfood.dk
-
To unsubscribe, e-mail: docs-unsubscr...@h
at default charset change reverted (at least for the
httpd site). If anyone wants to make a compelling argument in favor of
going utf-8, that's something for another day imho.
vh
Mads Toftum
--
http://soulfood.dk
-
To unsub
s that?
> Let me know if you'd like to receive a copy of the data.
>
Yes please.
vh
Mads Toftum
--
http://soulfood.dk
-
To unsubscribe, e-mail: docs-unsubscr...@httpd.apache.org
For additional commands, e-mail: docs-h...@httpd.apache.org
t before $work got in
the way. Fairly simple to do.
vh
Mads Toftum
--
http://soulfood.dk
-
To unsubscribe, e-mail: docs-unsubscr...@httpd.apache.org
For additional commands, e-mail: docs-h...@httpd.apache.org
;re going to go with a simple site created using doap, then you
shouldn't worry too much about usernames and passwords. If we want to
bring the accounts back and have a management system again, then we can
always extract the data at that point.
vh.
Mads To
opinions about it?
>
IMHO that's overkill. The site very rarely changes and there's no
shortage of people able to understand the current system.
Keeping versions up to date of (api)docs and getting modules.a.o
replaced is probably a better use of time.
vh
Mads
users if the error at
runtime (and build time also) isn't very clear on why modules fail to
load / build.
vh
Mads Toftum
--
http://soulfood.dk
-
To unsubscribe, e-mail: docs-unsubscr...@httpd.apache.org
For a
, and get rid of translations of things (authnz,
> logging, proxy) that we know for certain has radically changed in the last
> few years, while leaving things like the index files that may still be
> worthwhile.
>
+1 on principle although I prefer to keep transla
tting a second set of trusted
eyes on it before backporting. But I don't think it's a good idea to go
fishing for reviews at random spots like users@.
vh
Mads Toftum
--
http://soulfood.dk
-
To unsubscribe, e-mail:
t;
Agreed 100%. Most of the credit goes to Ralf S Engelschall who wrote
mod_ssl and most of the docs in question. Little has happened to them
since then. I think some of the assertions come from people who don't
appreciate his style of writing - much of his original mod_rewrite
documentation
nly coloring code and if
we must, some of the larger Configuration examples.
vh
Mads Toftum
--
http://soulfood.dk
-
To unsubscribe, e-mail: docs-unsubscr...@httpd.apache.org
For additional commands, e-mail: docs-h...@httpd.apache.org
more, no less. Hooking up with svnpubsub most likely
makes sense. As for the rest of the site, the parts that aren't in the
manual, that's another story which probably belongs on dev@ rather than
here.
vh
Mads Toftum
--
http://soulfood.dk
-
Given that
you're already planning to solve 0-effort contributions, I don't see the
gain in changing the toolset. We'd still have a committer requirement
for using the CMS, so it's not opening up for wider contributions
anyway.
vh
Mads Toftum
--
http://soulfood.dk
---
e asf policy.
vh
Mads Toftum
--
http://flickr.com/photos/q42/
-
To unsubscribe, e-mail: docs-unsubscr...@httpd.apache.org
For additional commands, e-mail: docs-h...@httpd.apache.org
rather more
> complicated than just a link to Github, but any barrier that we can
> remove would be good.
>
Given the commenting system, I don't know how badly we need to add more
links. If anything, I'd much rather have it go to
http://httpd.apa
ess
> > is so rigorous, and it's hard to find reviewers.
>
> Maybe, maybe not. I think, the project itself lost traction in terms of
> contributions (from non-developers). It's not that cool anymore (or the hot
>
r1997534 - Cool Feature' sort of
> recap.
> Based on the audience for that news, they can drill down into the actual svn
> commit, or not.
>
> We already have a vehicle for transmitting all commit activity.
>
If anything, then do it as a different twitter user (same
obably get someone to run
the pages through google translate as a minimal validation.
vh
Mads Toftum
--
http://flickr.com/photos/q42/
-
To unsubscribe, e-mail: docs-unsubscr...@httpd.apache.org
For additional commands, e-mail: docs-h...@httpd.apache.org
89 matches
Mail list logo