This update doesn't actually include any security fixes (there's something I never thought I'd see;) ) - most of the improvements concern mod_proxy. Here's the full list:
HTTP/1.1 support for mod_proxy.
Other mod_proxy improvements.
The supplied icons are now also distributed in PNG format
The new 'FileETag' directive to allow one to build the format of the ETag via runtime directives.
Addition of a 'filter callback' function to enable modules to intercept the output byte stream for dynamic page caching.
I stand corrected - how embaressing:) I just re-checked and the page I was quoting had "Apache 1.3.23" at the top. I did a ctrl+refresh and the page changed to show the release notes for 1.3.24. Looks like either my browser was caching the old announcement page or I got caught out by my University's proxy. Not sure why the Apache project use the same URL for all of these announcements though.
My firm, Nüsse(tm) has recently gone ahead with their decision to incorporate both Apache, as well as support for the recently released RNTP protocol into our next generation product (discussed here).
The fact that so many security improvements have been made in the new release of Apache is great news for our consumer base, which includes United States Government.
Not really, considering that they use a readme.html instead of an actual index.html (the readme.html allows a directory listing along with other HTML text, very kewl IMHO).
-- "There is a way that seems right to a man, but its end is the way of death." Proverbs 16:25 (NKJV)
Yeah that is definitely cool. Here are some changes from the 1.3 changelog, which seems a lot more technical than the announcement:
Changes with Apache 1.3.24
*) Fixed a segfault in mod_include when #if, #elif, #else, or #endif
directives were improperly terminated. [Cliff Woolley]
*) Introduce proper escaping of command.com and cmd.exe for Win32.
These patches close vulnerability CAN-2002-0061, identified and
reported by Ory Segal , by which any CGI
invocation of.bat or.cmd files could comprimize the system
when the.bat or.cmd was parsed the query args as an argument
to either cmd.exe/c or command.com/c. [William Rowe]
*) Add % and \r [C/R] to the dangerous Win32 shell character list.
Retain the Unix sh escapes list for compatibility.
[William Rowe]
*) Pass the command line to the cmd.exe/c interpreter double quoted.
This fixes a bug that CGI args ending in a double-quote would
cause invocation to fail. Also, treat command.com as a 16-bit
executable. [William Rowe]
*) Win32; Never invoke cmd or bat scripts based on the registry, even
for 'ScriptInterpreterSource Registry' enabled. [William Rowe]
*) Provide Win32 users a log of the cgi command invoked, to assist
in debugging scripts at LogLevel info. Also provide env vars
at LogLevel debug for additional help to admins troubleshooting
the ever mysterious "Premature end of script headers" error.
[Aaron Bannert]
*) Added the 'CGICommandArgs off' directive, to allow admins
to disable the query argument passing mechanism in Apache,
if future CGI argument vulnerabilities should be discovered.
This defaults to 'on', meaning isindex-style query arguments
are enabled. [Aaron Bannert]
*) When a proxied site was being served, Apache was replacing
the original site Server header with it's own, which is not
allowed by RFC2616. Fixed. [Graham Leggett]
*) Fixed the previous multiple-cookie fix in the proxy. Cookies
are broken in that they contain dates which in turn contain
commas - so merging and then unmerging them breaks Set-Cookie
headers. Sigh. [Graham Leggett]
*) Add ap_uuencode to the httpd.exp exports file used by
the AIX linker. [Bill Stoddard]
*) Win32: Ignore AcceptMutex directive if it is present
[Bill Stoddard]
*) mod_rewrite: restored rnd behavior that was broken in 1.3.23.
PR 10090, 10185 [Jeroen Boomgaardt ]
*) NetWare: Added the command line directive -e that forces all
fatal configuration error messages to the logger screen rather
than the Apache screen before Apache is unloaded.
[Brad Nicholes bnicholes@novell.com]
*) Add the ProxyIOBufferSize option. Previously the size of the
buffer used while reading from the remote server in proxy was
taken from ProxyReceiveBufferSize. [Graham Leggett]
*) Fix a NULL variable check in proxy where we were checking the
wrong variable. [Geff Hanoian ]
*) Fix typo in default config files related to Swedish language
documents. PR: 9906, 10040 [Tomas Ögren,
Dennis Lundberg ]
*) apxs didn't get rebuilt when options were changed. This must have
caused much puzzlement in the past. Fixed.
[Ben Laurie]
*) No idea why an HTTP/1.1 proxy would send an HTTP/1.0 request
to a remote server by default. Fixed.
[Graham Leggett, Gabriel Russell ]
*) NetWare: Added the module mod_log_nw to handle log rotation.
This module adds LogRotateDaily and LogRotateInterval to allow
all of the custom logs to be either rotated on a daily basis or
on a specific interval. Based on a patch by Bertrand Demiddelaer.
[Brad Nicholes bnicholes@novell.com]
*) Fix typo in rotatelogs.8. [Will Lowe ]
*) Clean up warnings in mod_proxy [Chuck Murcko ]
*) TPF: Use the correct subpool when opening the error log.
This prevents a possible SIGPIPE in standalone_main.
[David McCreedy ]
*) When proxy enabled a slow frontend client to read from an
expensive backend server, it would wait until it had delivered
the response to the slow frontend client completely before
closing the backend connection. The backend connection is now
closed as soon as the last byte is read from it, freeing up
resources that would have been tied up unnecessarily.
[Graham Leggett, Igor Sysoev ]
*) The proxy code read chunks from the backend server in a
hardcoded amount of 8k. The existing ProxyReceiveBufferSize
parameter has been overloaded to specify the size of this buffer.
[Graham Leggett, Igor Sysoev ]
*) [Security] Prevent invalid client hostnames from appearing in
the log file. If a double-reverse lookup was performed (e.g.,
for an "Allow from.my.domain" directive) but failed, then
a spoofed dns-reverse-address could appear in the logs. Now
the numeric address is logged instead. Note that
reverse-address-spoofing did NOT actually allow access
to any protected resource! [Martin Kraemer]
*) Some browsers ignore cookies that have been merged into a
single Set-Cookie header. Set-Cookie and Set-Cookie2 headers
are now unmerged in the http proxy before being sent to the
client. [Graham Leggett]
*) Fix a problem with proxy where each entry of a duplicated
header such as Set-Cookie would overwrite and obliterate the
previous value of the header, resulting in multiple header
values (like cookies) going missing.
[Graham Leggett, Joshua Slive]
*) Fix a problem with proxy where X-Cache headers were
overwriting and then obliterating upstream X-Cache headers
from other proxies.
[Graham Leggett, Jacob Rief ]
*) Win32: Work around a bug in Windows XP that caused data
corruption on writes to the network. The WinXP bug
is tickled by the combined use of WSADuplicateSocket
and blocking send() calls.
[Bill Stoddard, Bill Rowe, Allan Edwards, Szabolcs Szakacsits]
*) Add 'IgnoreCase' keyword to the IndexOptions directive;
if active, upper- and lower-case letters are insignificant
in ordering. In other words, all A* and a* files will be
listed together, rather than the a* ones after all the [A-Z]*
ones. [Tullio Andreatta ]
*) NetWare: Implemented the real ap_os_case_canonical_filename()
function that retrieves the accurately cased path and file
name from the file system. [Brad Nicholes bnicholes@novell.com]
*) Fix the longstanding bug that errors (returned by src/Configure)
would not be noticed by the top level configure script.
That was bad for automated configurations. [Martin Kraemer]
*) Link with -lpthread on Solaris since we reference pthread
functions for the accept mutex. Previously, the link step
would succeed but we would link to bogus versions of the
pthread functions in libc, apparently breaking accept mutex
serialization when "AcceptMutex pthread" was used and
apparently breaking some third-party modules whether
or not "AcceptMutex pthread" was used. [Jeff Trawick]
*) The Location: response header field, used for external
redirect, *must* be an absoluteURI. The Redirect directive
tested for that, but RedirectMatch didn't -- it would allow
almost anything through. Now it will try to turn an abs_path
into an absoluteURI, but it will correctly varf like Redirect
if the final redirection target isn't an absoluteURI. [Ken Coar]
*) apxs: fix bug that prevented -S option from containing quotes.
[Ben Laurie]
*) ftp proxy: various cosmetic and functional improvements
- Allow for/%2f hack (to access the root directory / )
- properly escape generated links in dir listing
- do directory listings in ASCII, to avoid problems with EBCDIC
servers
- close data & control channels to server properly
[Martin Kraemer]
*) NetWare: Added mod_auth_dbm to the project file.
[Brad Nicholes bnicholes@novell.com]
Actually, you appear to have not read the announcement.
Apache 1.3.24 Major changes
Security vulnerabilities
The main security vulnerabilities addressed in 1.3.24 are:
Fix the security vulnerability noted in CAN-2002-0061 (mitre.org)
regarding the escaping of command line args on Win32.
Prevent invalid client hostnames from appearing in the log file.
New features
The main new features in 1.3.24 (compared to 1.3.23) are:
Various mod_proxy improvements, such as the new
ProxyIOBufferSize directive
The new IgnoreCase keyword to the
IndexOptions directive.
New features that relate to specific platforms:
Added the module mod_log_nw to handle log rotation
under NetWare
Bugs fixed
The following bugs were found in Apache 1.3.23 and have been fixed in
Apache 1.3.24:
mod_rewrite's rnd was broken and has been fixed.
The -S option of apxs was not able to
handle quotes; also apxs
is now rebuilt when options are changed.
proxy now correctly handles Cookies and
X-Cache headers.
The following bugs relate to specific platforms:
Fixed a problem in TPF when we were using the wrong subpool when
opening the error log.
pthread accept() mutexes on Solaris were broken
(since we were not linking against pthread)
-- rooooar
Are you kidding?
by
Anonymous Coward
·
· Score: 0
This is the biggest story ever! I can't wait until 1.3.24.1 comes out!! I'll be hitting the refresh button continuously in anticipation!!!
beware, 1.3.24 has mod_proxy probelms. :-(
by
beb
·
· Score: 1
If you are planning on using mod_proxy, I would recommend sticking with 1.3.20, or wait until 1.3.25 is released. Why? The new mod_proxy code has a bug which won't "downgrade" HTTP 1.1 responses sent from the proxy to upstream HTTP servers. Which means if you have a HTTP 1.0 browser (Netscape 4.*) and you access a site proxied with Apache 1.3.24 (or anything past 1.3.21 methinks) you will get a bunch of garbage displayed on the page (the HTTP 1.1 "de-chunking" byte markers)
Slashdot Mirror
What was wrong with the Apaches before? They are the best---oh, not the helicopters?
Oh, sorry, I should be in the "Southern Militia Forum"
Someone ever tries to kill you, you try to kill them right back!
- HTTP/1.1 support for mod_proxy.
- Other mod_proxy improvements.
- The supplied icons are now also distributed in PNG format
- The new 'FileETag' directive to allow one to build the format of the ETag via runtime directives.
- Addition of a 'filter callback' function to enable modules to intercept the output byte stream for dynamic page caching.
There are a few platform specific fixes as well.rooooar
This is the biggest story ever! I can't wait until 1.3.24.1 comes out!! I'll be hitting the refresh button continuously in anticipation!!!
If you are planning on using mod_proxy, I would recommend sticking with 1.3.20, or wait until 1.3.25 is released. Why? The new mod_proxy code has a bug which won't "downgrade" HTTP 1.1 responses sent from the proxy to upstream HTTP servers. Which means if you have a HTTP 1.0 browser (Netscape 4.*) and you access a site proxied with Apache 1.3.24 (or anything past 1.3.21 methinks) you will get a bunch of garbage displayed on the page (the HTTP 1.1 "de-chunking" byte markers)
= 7513
= 7195
= 7572
Here's the bug:
http://nagoya.apache.org/bugzilla/show_bug.cgi?id
Also, the 1.3.24 mod_proxy code so far still has the following bugs:
http://nagoya.apache.org/bugzilla/show_bug.cgi?id
(mod_proxy munches cookies if number of cookies > 1)
http://nagoya.apache.org/bugzilla/show_bug.cgi?id
(mod_proxy ignores "Timeout" directive and cuts off long up/downloads)
Even the best of software have its share of bugs.