I've got the 2.0.18 (+proxy) running on Solaris 2.8
Reverse Proxying is working
I'm seeing some problems going to apple.com and cnet.com (the akamai thing)
I don't think this should hold up building a single tarball, we just need
to stick a note that akamized sites won't work with properly
..Ian
> -----Original Message-----
> From: William A. Rowe, Jr. [mailto:[EMAIL PROTECTED]]
> Sent: Fri, May 18, 2001 3:16 PM
> To: [EMAIL PROTECTED]; William A. Rowe, Jr.
> Subject: Re: Tagging Apache 2.0 for beta candidate
>
>
> From: "William A. Rowe, Jr." <[EMAIL PROTECTED]>
> Sent: Friday, May 18, 2001 4:58 PM
>
>
> > From: "Bill Stoddard" <[EMAIL PROTECTED]>
> > Sent: Friday, May 18, 2001 3:22 PM
> >
> > I'm not suggesting we retag the httpd-2.0 tree!!! Just
> provide a single tarball
> > for folks to jump on this module in this beta.
> >
> > > Since the tree is relatively stable now and we do not
> freeze development before
> > > tagging a tree, now seems to be a good time to try for a beta.
> > > It is not a big deal to roll the proxy
> > > tarball and make it available to work with 2.0.18. We can
> include it next
> > > time around.
> >
> > Why not simply tag proxy, [SAME TAG!] and add it to the
> tarball? How hard
> > is that?
>
> I've just slapped the APACHE_2_0_18 tag on the httpd-proxy
> tree, effective the same
> timetable as httpd-2.0's tag.
>
> If the modproxy folks want to check out the proxy tree, grab
> the tarball, insert
> proxy-2.0 into that package, and retar it as
> httpd-proxy-2.0.18.tar I believe that
> could make everyone happy, no?
>
> If that package isn't up to snuff, then we release the
> non-proxy tarball as the
> beta, instead. And ITMT figure out how to release a single
> tarball easily.
>
> Since FirstBill has limited time, it's not too much to ask
> this of proxy folk,
> who are more ready to assure the package builds.
>
> Objections?
>
> Bill
>
