You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by rb...@covalent.net on 2001/07/09 04:53:13 UTC
Apache 2.0.20
I have just tagged Apache 2.0.20, and I am rolling it now. It will
be available at http://dev.apache.org/dist/ within the next 30
minutes. Please feel free test and report back the results.
Ryan
_____________________________________________________________________________
Ryan Bloom rbb@apache.org
Covalent Technologies rbb@covalent.net
-----------------------------------------------------------------------------
RE: Apache 2.0.20
Posted by Mladen Turk <ml...@mail.inet.hr>.
> -----Original Message-----
> From: Sebastian Bergmann [mailto:sb@sebastian-bergmann.de]
> Sent: 09. srpanj 2001 00:39
> To: new-httpd@apache.org
> Subject: Re: Apache 2.0.20
>
> rbb@covalent.net wrote:
> > I have just tagged Apache 2.0.20, and I am rolling it now. It will
> > be available at http://dev.apache.org/dist/ within the next 30
> > minutes. Please feel free test and report back the results.
[Mladen Turk]
Inside mpm/winnt/service.c (service_nt_main)
replace the mpm_new_argv->cont
with mpm_new_argv->pool.
Then it works.
Mladen Turk
MCSE/GIS Specialist
Sisiceva 10,
10000 Zagreb, Croatia
mailto:[ mturk@mappingsoft.com ]
http://apache.mappingsoft.com
Re: Apache 2.0.20
Posted by Sebastian Bergmann <sb...@sebastian-bergmann.de>.
rbb@covalent.net wrote:
> I have just tagged Apache 2.0.20, and I am rolling it now. It will
> be available at http://dev.apache.org/dist/ within the next 30
> minutes. Please feel free test and report back the results.
I did a CVS checkout after your Apache 2.0.20 announcement. I was not
able to build it on Win32.
Have a look at
http://www.sebastian-bergmann.de/make.txt
for MS Visual Studio 6's output of warnings and errors.
I only have a german copy of VisualStudio, so the error messages are
in German - sorry :-(
--
sebastian bergmann http://www.sebastian-bergmann.de/
Re: 2.0.20/SSI problem?
Posted by Ian Holsman <ia...@cnet.com>.
On 09 Jul 2001 15:24:59 -0400, Dale Ghent wrote:
>
> I just compiled .20 up from the tarball, and all seems great except when
> it comes to serving SSI (.shtml) pages.
>
> It looks like the SSI parsing goes okay, but the Content-Type header
> that's being returned is "text/plain" instead of the expected "text/html",
> thus causing the browser to show the page in it's source form.
>
Hi Dale,
I just pulled the latest CVS and I get text/html in the header.
My config
...
Options FollowSymLinks +Includes
...
AddType text/html .shtml
<FilesMatch "\.shtml(\..+)?$">
SetOutputFilter INCLUDES
</FilesMatch>
> I'm using the stock httpd.conf, with the SSI-related config container
> uncomented and "IncludesNoExec" added to the relevant directorie's
> Options. The shtml pages in question exist on a name-based vhost that's
> tacked onto the bottom of the config and has no directive in it that would
> seem to get in the way for SSI being read. The same config runs just fine
> on 1.3.x
>
> /dale
>
--
Ian Holsman
Performance Measurement & Analysis
CNET Networks - 415 364-8608
Re: 2.0.20/SSI problem?
Posted by rb...@covalent.net.
On Mon, 9 Jul 2001, Dale Ghent wrote:
> On Mon, 9 Jul 2001, Dale Ghent wrote:
>
> |
> | I just compiled .20 up from the tarball, and all seems great except when
> | it comes to serving SSI (.shtml) pages.
> |
> | It looks like the SSI parsing goes okay, but the Content-Type header
> | that's being returned is "text/plain" instead of the expected "text/html",
> | thus causing the browser to show the page in it's source form.
>
> Cliff suggested that I add an "AddType text/html .shtml" to my config, and
> boom, it worked.
>
> I guess that I'm under the impression that mod_include should set the
> Content-Type? Or is this AddType statement just missing from
> http-std.conf?
This is just missing from the standard config file.
Ryan
_____________________________________________________________________________
Ryan Bloom rbb@apache.org
Covalent Technologies rbb@covalent.net
-----------------------------------------------------------------------------
Re: 2.0.20/SSI problem?
Posted by Cliff Woolley <cl...@yahoo.com>.
On Mon, 9 Jul 2001, Dale Ghent wrote:
> I guess that I'm under the impression that mod_include should set the
> Content-Type?
In theory, it's possible to parse non-html documents with mod_include. In
that case, you'd want to have explicit control over the content type
rather than leaving it up to mod_include to set it for you.
> Or is this AddType statement just missing from http-std.conf?
Yep. It was there in 1.3's default config file (commented out)...
--Cliff
--------------------------------------------------------------
Cliff Woolley
cliffwoolley@yahoo.com
Charlottesville, VA
Re: 2.0.20/SSI problem?
Posted by Dale Ghent <da...@elemental.org>.
On Mon, 9 Jul 2001, Dale Ghent wrote:
|
| I just compiled .20 up from the tarball, and all seems great except when
| it comes to serving SSI (.shtml) pages.
|
| It looks like the SSI parsing goes okay, but the Content-Type header
| that's being returned is "text/plain" instead of the expected "text/html",
| thus causing the browser to show the page in it's source form.
Cliff suggested that I add an "AddType text/html .shtml" to my config, and
boom, it worked.
I guess that I'm under the impression that mod_include should set the
Content-Type? Or is this AddType statement just missing from
http-std.conf?
/dale
Re: 2.0.20/SSI problem?
Posted by Cliff Woolley <cl...@yahoo.com>.
On Mon, 9 Jul 2001, Dale Ghent wrote:
> It looks like the SSI parsing goes okay, but the Content-Type header
> that's being returned is "text/plain" instead of the expected "text/html",
> thus causing the browser to show the page in it's source form.
As I mentioned off-list, all you have to do is add an addtype line to your
config:
AddType text/html .shtml
We might want to add that to the default config file.
--Cliff
--------------------------------------------------------------
Cliff Woolley
cliffwoolley@yahoo.com
Charlottesville, VA
2.0.20/SSI problem?
Posted by Dale Ghent <da...@elemental.org>.
I just compiled .20 up from the tarball, and all seems great except when
it comes to serving SSI (.shtml) pages.
It looks like the SSI parsing goes okay, but the Content-Type header
that's being returned is "text/plain" instead of the expected "text/html",
thus causing the browser to show the page in it's source form.
I'm using the stock httpd.conf, with the SSI-related config container
uncomented and "IncludesNoExec" added to the relevant directorie's
Options. The shtml pages in question exist on a name-based vhost that's
tacked onto the bottom of the config and has no directive in it that would
seem to get in the way for SSI being read. The same config runs just fine
on 1.3.x
/dale
Re: Apache 2.0.20
Posted by "William A. Rowe, Jr." <wr...@rowe-clan.net>.
From: "Bill Stoddard" <bi...@wstoddard.com>
Sent: Monday, July 09, 2001 9:32 AM
> The obvious just occured to me. Greg Ames should get this running on apache.org and if it
> holds up, then declare a beta.
Hope the wound left when the obvious bit you heals quickly :-)
+1 on declaring the beta based on 3 days of stable apache.org gruntwork.
Re: Apache 2.0.20
Posted by Greg Ames <gr...@remulak.net>.
On Monday 09 July 2001 10:32, Bill Stoddard wrote:
> The obvious just occured to me. Greg Ames should get this running on
> apache.org and if it holds up, then declare a beta.
>
> Bill
>
We are currently running apache.org with code out of CVS from Friday PM. My
post on the subject went into the bit bucket due to a config error on my new
email client :-( This should be pretty close to the tarball.
Unfortunately graceful restart occasionally fail on prefork. Manoj and Brian
had to restart Apache manually a couple of times, so I'm moving us back to
the prior build in a bit. Jeff was able to reproduce this problem at least
once, and said something about the accept mutexes looking bogus.
Greg
Re: Apache 2.0.20
Posted by Bill Stoddard <bi...@wstoddard.com>.
The obvious just occured to me. Greg Ames should get this running on apache.org and if it
holds up, then declare a beta.
Bill
> Compiles and seems to work pretty good on AIX (start/stop/serves static pages, serves
> CGIs, restarts under load). Too bad it doesn;t compile on Windows.
>
> +1 on making this a beta.
>
> Bill
>
> >
> > I guess I should mention that I have compiled and run this beta on my
> > Mandrake 7.2 box, and apache.org (FreeBSD) while testing before I tagged
> > and rolled.
> >
> > So, I'm +1 for making this a beta too.
> >
> > Ryan
> >
> > On Sun, 8 Jul 2001, Justin Erenkrantz wrote:
> >
> > > On Sun, Jul 08, 2001 at 07:53:13PM -0700, rbb@covalent.net wrote:
> > > >
> > > > I have just tagged Apache 2.0.20, and I am rolling it now. It will
> > > > be available at http://dev.apache.org/dist/ within the next 30
> > > > minutes. Please feel free test and report back the results.
> > >
> > > That tarball compiles and comes up fine on my Mandrake 8.0 box (Linux
> > > 2.4, glibc 2.2). The MPM doesn't kill itself this time around. =)
> > >
> > > +1 for making this beta (FWIW). -- justin
> > >
> > >
> > >
> >
> >
> > _____________________________________________________________________________
> > Ryan Bloom rbb@apache.org
> > Covalent Technologies rbb@covalent.net
> > -----------------------------------------------------------------------------
> >
>
Re: Apache 2.0.20
Posted by Bill Stoddard <bi...@wstoddard.com>.
Compiles and seems to work pretty good on AIX (start/stop/serves static pages, serves
CGIs, restarts under load). Too bad it doesn;t compile on Windows.
+1 on making this a beta.
Bill
>
> I guess I should mention that I have compiled and run this beta on my
> Mandrake 7.2 box, and apache.org (FreeBSD) while testing before I tagged
> and rolled.
>
> So, I'm +1 for making this a beta too.
>
> Ryan
>
> On Sun, 8 Jul 2001, Justin Erenkrantz wrote:
>
> > On Sun, Jul 08, 2001 at 07:53:13PM -0700, rbb@covalent.net wrote:
> > >
> > > I have just tagged Apache 2.0.20, and I am rolling it now. It will
> > > be available at http://dev.apache.org/dist/ within the next 30
> > > minutes. Please feel free test and report back the results.
> >
> > That tarball compiles and comes up fine on my Mandrake 8.0 box (Linux
> > 2.4, glibc 2.2). The MPM doesn't kill itself this time around. =)
> >
> > +1 for making this beta (FWIW). -- justin
> >
> >
> >
>
>
> _____________________________________________________________________________
> Ryan Bloom rbb@apache.org
> Covalent Technologies rbb@covalent.net
> -----------------------------------------------------------------------------
>
Re: Apache 2.0.20
Posted by rb...@covalent.net.
I guess I should mention that I have compiled and run this beta on my
Mandrake 7.2 box, and apache.org (FreeBSD) while testing before I tagged
and rolled.
So, I'm +1 for making this a beta too.
Ryan
On Sun, 8 Jul 2001, Justin Erenkrantz wrote:
> On Sun, Jul 08, 2001 at 07:53:13PM -0700, rbb@covalent.net wrote:
> >
> > I have just tagged Apache 2.0.20, and I am rolling it now. It will
> > be available at http://dev.apache.org/dist/ within the next 30
> > minutes. Please feel free test and report back the results.
>
> That tarball compiles and comes up fine on my Mandrake 8.0 box (Linux
> 2.4, glibc 2.2). The MPM doesn't kill itself this time around. =)
>
> +1 for making this beta (FWIW). -- justin
>
>
>
_____________________________________________________________________________
Ryan Bloom rbb@apache.org
Covalent Technologies rbb@covalent.net
-----------------------------------------------------------------------------
Re: Apache 2.0.20
Posted by Justin Erenkrantz <je...@ebuilt.com>.
On Sun, Jul 08, 2001 at 07:53:13PM -0700, rbb@covalent.net wrote:
>
> I have just tagged Apache 2.0.20, and I am rolling it now. It will
> be available at http://dev.apache.org/dist/ within the next 30
> minutes. Please feel free test and report back the results.
That tarball compiles and comes up fine on my Mandrake 8.0 box (Linux
2.4, glibc 2.2). The MPM doesn't kill itself this time around. =)
+1 for making this beta (FWIW). -- justin
Re: Apache 2.0.20
Posted by "William A. Rowe, Jr." <wr...@rowe-clan.net>.
From: "Daniel Stone" <da...@sfarc.net>
Sent: Tuesday, July 10, 2001 6:06 AM
> On Sun, Jul 08, 2001 at 07:53:13PM -0700, rbb@covalent.net wrote:
> >
> > I have just tagged Apache 2.0.20, and I am rolling it now. It will
> > be available at http://dev.apache.org/dist/ within the next 30
> > minutes. Please feel free test and report back the results.
>
> -1 on making this a beta, until either mod_ssl is a) fixed, b) tagged
> experimental/broken/whatever, or c) ripped out. Yes, I've applied the two
> patches that were floating around earlier, and it segfaults on load. Mind
> you, there's no clear documentation on making this happen, but I used the
> configuration directives and userspace tools from 1.3.20+mod_ssl, and it all
> works fine, except it segfaults on load. Backtrace soon(ish).
As others have pointed out, we are proceeding on the beta w/w-o mod_ssl.
Other issues may interfere with this becoming a beta, but this lists' long
debate yeilding the decision to proceed. BUT, your objection should be noted
in the beta announcement (something like, "Note; mod_ssl is not part of this
beta cycle, and is not even asmuch as alpha quality yet. Please be patient
for ssl/tls support in Apache 2.0.")
As another noted, mod_tls works. However, mod_tls is a model of how mod_ssl
should insert itself as a filter in the Apache 2.0 model. The 'cool features'
are actually part of mod_ssl and will remain there. mod_tls is very light on
useful functionallity, and it won't be growing new Directives.
Bill
Re: Apache 2.0.20
Posted by Cliff Woolley <cl...@yahoo.com>.
On Tue, 10 Jul 2001, Daniel Stone wrote:
> -1 on making this a beta, until either mod_ssl is a) fixed, b) tagged
> experimental/broken/whatever, or c) ripped out.
I though we decided that we WOULD NOT hold up a beta for mod_ssl. (b) is
essentially already done, though perhaps not advertised enough.
I'm -1 for waiting for (a) or (c) to get a beta out.
--Cliff
--------------------------------------------------------------
Cliff Woolley
cliffwoolley@yahoo.com
Charlottesville, VA
Re: Apache 2.0.20
Posted by Daniel Stone <da...@sfarc.net>.
On Sun, Jul 08, 2001 at 07:53:13PM -0700, rbb@covalent.net wrote:
>
> I have just tagged Apache 2.0.20, and I am rolling it now. It will
> be available at http://dev.apache.org/dist/ within the next 30
> minutes. Please feel free test and report back the results.
-1 on making this a beta, until either mod_ssl is a) fixed, b) tagged
experimental/broken/whatever, or c) ripped out. Yes, I've applied the two
patches that were floating around earlier, and it segfaults on load. Mind
you, there's no clear documentation on making this happen, but I used the
configuration directives and userspace tools from 1.3.20+mod_ssl, and it all
works fine, except it segfaults on load. Backtrace soon(ish).
d
--
Daniel Stone <da...@sfarc.net>
<Nuke> "can NE1 help me aim nuclear weaponz????? /MSG ME!!"
Re: Apache 2.0.20
Posted by Daniel Stone <da...@sfarc.net>.
On Sun, Jul 08, 2001 at 07:53:13PM -0700, rbb@covalent.net wrote:
>
> I have just tagged Apache 2.0.20, and I am rolling it now. It will
> be available at http://dev.apache.org/dist/ within the next 30
> minutes. Please feel free test and report back the results.
-1 on making this a beta, until either mod_ssl is a) fixed, b) tagged
experimental/broken/whatever, or c) ripped out. Yes, I've applied the two
patches that were floating around earlier, and it segfaults on load. Mind
you, there's no clear documentation on making this happen, but I used the
configuration directives and userspace tools from 1.3.20+mod_ssl, and it all
works fine, except it segfaults on load. Backtrace soon(ish).
d
--
Daniel Stone <da...@sfarc.net>
<Nuke> "can NE1 help me aim nuclear weaponz????? /MSG ME!!"
Re: Apache 2.0.20
Posted by Jeff Trawick <tr...@attglobal.net>.
rbb@covalent.net writes:
> I have just tagged Apache 2.0.20, and I am rolling it now. It will
> be available at http://dev.apache.org/dist/ within the next 30
> minutes. Please feel free test and report back the results.
I'm running HEAD, but the only thing I see changed after the tag is
ap_release.h.
This is with threaded on Linux, using defaults for all threaded.c
configuration directives.
Beat on the server for a while (e.g., 100,000 requests for a static
file over 20 concurrent connections, single request per connection)
Once the requests are completed (i.e., server stops being busy):
[Mon Jul 09 10:18:24 2001] [info] server seems busy, (you may need to increase StartServers, ThreadsPerChild or Min/MaxSpareThreads),
spawning 8 children, there are around 42 idle threads, and 6 total children
[Mon Jul 09 10:18:29 2001] [notice] child pid 14925 exit signal Segmentation fault (11)
[Mon Jul 09 10:18:29 2001] [notice] child pid 14891 exit signal Segmentation fault (11)
[Mon Jul 09 10:18:29 2001] [notice] child pid 14889 exit signal Segmentation fault (11)
Obviously this should be resolved before a beta since folks want this
to be a good release of the threaded MPM.
--
Jeff Trawick | trawick@attglobal.net | PGP public key at web site:
http://www.geocities.com/SiliconValley/Park/9289/
Born in Roswell... married an alien...