From jyri@sac.sfbay.sun.com Fri Oct 16 10:07:01 2009
Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n9GH70AA007165
	for <LSARC-ext@sac.sfbay.sun.com>; Fri, 16 Oct 2009 10:07:00 -0700 (PDT)
Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11])
	by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n9GH6s5F002899;
	Fri, 16 Oct 2009 18:06:59 +0100 (BST)
Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by
 brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0KRM0080PA7KNK00@brm-avmta-1.central.sun.com>; Fri,
 16 Oct 2009 11:06:56 -0600 (MDT)
Received: from dm-sfbay-02.sfbay.sun.com ([129.146.11.31])
 by brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0KRM000JJA7KKC70@brm-avmta-1.central.sun.com>; Fri,
 16 Oct 2009 11:06:56 -0600 (MDT)
Received: from sac.sfbay.sun.com (sac.SFBay.Sun.COM [129.146.226.132])
	by dm-sfbay-02.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.4)
 with ESMTP id n9GH6t1c018176; Fri, 16 Oct 2009 10:06:55 -0700 (PDT)
Received: from sac.sfbay.sun.com (localhost [127.0.0.1])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n9GH6si7007160; Fri,
 16 Oct 2009 10:06:54 -0700 (PDT)
Received: (from jyri@localhost)	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8/Submit)
 id n9GH6ssx007156; Fri, 16 Oct 2009 10:06:54 -0700 (PDT)
Date: Fri, 16 Oct 2009 10:06:54 -0700 (PDT)
From: Jyri Virkki <jyri@sac.sfbay.sun.com>
Subject: Update Apache HTTP Server to 2.2.14 [LSARC/2009/565 Self Review]
To: LSARC-ext@sun.com
Cc: webstack-discuss@opensolaris.org
Message-id: <200910161706.n9GH6ssx007156@sac.sfbay.sun.com>
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.4.1.325704
Status: RO
Content-Length: 3547



I am sponsoring this case for Seema Alevoor and closing it as approved
automatic. It's a straightforward Apache version update.


Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI
This information is Copyright 2009 Sun Microsystems
1. Introduction
    1.1. Project/Component Working Name:
	 Update Apache HTTP Server to 2.2.14
    1.2. Name of Document Author/Supplier:
	 Author:  Seema Alevoor
    1.3  Date of This Document:
	16 October, 2009
4. Technical Description

Update Apache HTTP Server to 2.2.14

1. Introduction
    1.1. Project/Component Working Name:

         Update Apache HTTP Server to 2.2.14

    1.2. Name of Document Author/Supplier:

         Author:  Seema Alevoor  (seema.alevoor@sun.com)

    1.3  Date of This Document:

         16 October, 2009

2. Summary

    2.1. Update Apache to 2.2.14

         Apache has released the next stable version, 2.2.14, this
         project updates the integrated Apache version to 2.2.14. [1][2]

         This version includes a number of general bug fixes and few security
         fixes.
   
         Also, this version includes a new module, "mod_proxy_scgi" [4]. This
         provides support for the SCGI protocol, version 1.

         Apache 2.2.14 ChangeLog can be found here:
         http://www.apache.org/dist/httpd/CHANGES_2.2.14
    
3. Technical Description

    3.1 New module, "mod_proxy_scgi"

         Apache HTTP Server version 2.2.14, includes a new module,
         "mod_proxy_scgi" [4]. It provides support for the SCGI protocol,
         version 1 and it depends on "mod_proxy" module.

         This module will not be enabled by default. This project will
         provide a sample configuration file, "mod_proxy_scgi.conf"
         within /etc/apache2/[version]/samples-conf.d directory. To
         enable this module, user will copy this sample file to
         /etc/apache2/[version]/conf.d directory and update the
         directives to specify the address of the SCGI application and
         the web server URI where it should be accessed. 

    3.2. New Configuration Directives

         "mod_proxy_scgi" apache module introduces two new configuration
         directives as listed below.

         "ProxySCGIInternalRedirect" Directive: This directive enables the
         backend to internally redirect the gateway to a different URL.
         
         "ProxySCGISendfile" Directive: This directive enables the SCGI backend
         to let files serve directly by the gateway.

         More information on these directives can be found here:
         http://httpd.apache.org/docs/2.2/mod/mod_proxy_scgi.html

4. Interfaces

    3.1. Exported Interfaces

    NAME                            STABILITY      NOTES
    ---------------------------------------------------------------------------
    ProxySCGIInternalRedirect       Uncommitted    mod_proxy_scgi configuration
                                                   directive
    ProxySCGISendfile               Uncommitted    mod_proxy_scgi configuration
                                                   directive



5.  References

    [1] http://httpd.apache.org/
    [2] http://httpd.apache.org/download.cgi
    [3] http://www.apache.org/dist/httpd/CHANGES_2.2.14
    [4] http://httpd.apache.org/docs/2.2/mod/mod_proxy_scgi.html
    [5] http://arc.opensolaris.org/caselog/LSARC/2009/020/



6. Resources and Schedule
    6.4. Steering Committee requested information
   	6.4.1. Consolidation C-team Name:
		sfw
    6.5. ARC review type: Automatic
    6.6. ARC Exposure: open


