Yes... it appears to have been intermediary caches that threw me... the 2.4 and 2.2 new vulnerabilities are now in sync on the site.
Thanks for confirming, Joe. On Mar 26, 2014 5:25 PM, "Joe Schaefer" <[email protected]> wrote: > What is the specific issue Bill- afaict everything looks fine to me. > > > > > On Wednesday, March 26, 2014 6:17 PM, William A. Rowe Jr. < > [email protected]> wrote: > > > On Mon, 17 Mar 2014 05:40:19 -0500 > > "William A. Rowe Jr." <[email protected]> wrote: > > > >> I've been running behind too... But expect to have all my platforms > >> checked out Monday. Since there are no negative votes we'll keep > >> this open a bit longer. > > > > Apologies for the delay, this has been pushed to the live site. > > > > Many thanks to rjung for the apr fixes already in 1.5.x branch which had > > confounded me (I noted the changes discussed here, and didn't look over > > for his earlier fixes). > > > > I cannot figure out what is going on with my attempt to refresh the > > http://httpd.apache.org/security/vulnerabilities_22.html page with the > > two new CVE's... if anyone can cast light on this, I'd much appreciate > > the guidance. > > >
