On ons, 2008-06-25 at 01:42 +0200, Henrik Nordstrom wrote:
> 2.7.STABLE3 has been rolled and is available for test. Unless some
> problem is found it will be signed, linked and pushed out to the ftp
> mirrors tomorrow (later today...)
>
> http://www.squid-cache.org/Versions/v
2.7.STABLE3 has been rolled and is available for test. Unless some
problem is found it will be signed, linked and pushed out to the ftp
mirrors tomorrow (later today...)
http://www.squid-cache.org/Versions/v2/2.7/squid-2.7.STABLE3.tar.bz2
(and .tar.gz)
Please test and report back any success
On sön, 2008-06-22 at 08:21 +1000, Mark Nottingham wrote:
> I'm going to produce a new patch for 2376 soon (along the lines
> discussed in comment 6); if that could get in it would be very good.
>
> Also, I'd like to see the patch in 2378 get in.
Both in.
Regards
Henrik
signature.asc
Descrip
I'm going to produce a new patch for 2376 soon (along the lines
discussed in comment 6); if that could get in it would be very good.
Also, I'd like to see the patch in 2378 get in.
Cheers,
On 21/06/2008, at 5:06 AM, Henrik Nordstrom wrote:
This is a last call to speak up now if there is any
This is a last call to speak up now if there is any pending patches you
think should be included in the next bugfix release. Me and Amos will be
releasing the next bugfix releases of 3.0 and 2.7 in a couple of days.
It's also a good time to speak up if there is any open bug reports which
deserves
ons 2008-04-02 klockan 01:12 +1300 skrev Amos Jeffries:
> 3 had the fix for major regression bug 2206 (407 ProxyAuth header missing).
Ah, right..
Regards
Henrik
ons 2008-04-02 klockan 01:27 +1300 skrev Amos Jeffries:
> That back-port is non-critical right? It's been broken for months.
More like days.. it was one of the patches you merged into Squid-3.0
just before 3.0.STABLE3...
> So it
> can wait a few days/weeks in the snapshots fo
On Tue, Apr 1, 2008 at 2:12 PM, Amos Jeffries <[EMAIL PROTECTED]> wrote:
> 3 had the fix for major regression bug 2206 (407 ProxyAuth header missing).
>
> Rolling back to s1 could cause those who patched it some trouble.
> That makes it 'b'. So ... Rolled STABLE4 with only this one patch on 3.
Henrik Nordstrom wrote:
tis 2008-04-01 klockan 23:34 +1300 skrev Amos Jeffries:
The fix will be in tomorrows daily snapshot.
I'm also repeating my pre-commit test cycle to see if I can figure how
this got through in the first place.
I propose we withdraw 3.0.STABLE3, and releas
Henrik Nordstrom wrote:
tis 2008-04-01 klockan 23:41 +1300 skrev Amos Jeffries:
As a maintainer, seeing STABLE3 not yet announced.
It's released the minute it's published.
Do you think, bug 2288 is one of these situations where we should bump a
stable4 out immediately?
W
tis 2008-04-01 klockan 23:41 +1300 skrev Amos Jeffries:
> As a maintainer, seeing STABLE3 not yet announced.
It's released the minute it's published.
> Do you think, bug 2288 is one of these situations where we should bump a
> stable4 out immediately?
Well.. with STABLE3 n
tis 2008-04-01 klockan 23:34 +1300 skrev Amos Jeffries:
> The fix will be in tomorrows daily snapshot.
>
> I'm also repeating my pre-commit test cycle to see if I can figure how
> this got through in the first place.
I propose we withdraw 3.0.STABLE3, and release 3.0.STABLE4
mån 2007-03-19 klockan 08:46 +0900 skrev Steven Wilton:
> Can anyone confirm whether request->my_addr should contain the IP address
> that the customer has connected to, or the IP address that the OS has
> redirected the packet to for requests that have been semnt to squid using
> NAT.
The two sh
> -Original Message-
> From: Steven Wilton [mailto:[EMAIL PROTECTED]
> Sent: Monday, 19 March 2007 8:46 AM
> To: squid-dev@squid-cache.org
> Subject: request->my_addr change from 2.6.STABLE3 to 2.6.STABLE10
>
> I've just discovered that due to
I've just discovered that due to the reworking of places that
ClientNatLookup is called, request->my_addr now contains the local IP of the
proxy server rather than the IP address of the web server the client thinks
it's talking to for transparent requests. I'm assuming that this was done
deliberat
2.6.STABLE3 has now been released.
Regards
Henrik
signature.asc
Description: Detta är en digitalt signerad meddelandedel
Think we are more or less set now for a stable3 release.
Please test the tree some extra. And if you know any issues you think
should be fixed for stable3 then now is a goot time to speak up.
Regards
Henrik
signature.asc
Description: Detta är en digitalt signerad meddelandedel
17 matches
Mail list logo