lp:~brotchie/squid/ssl-subjectAltName-3.1

Branch merges

Propose for merging

No branches dependent on this one.

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Related blueprints

9880. By James Brotchie <email address hidden> on 2010-02-03

Ported SSL cert handling of subjectAltName from Squid 2.7.

9879. By Amos Jeffries on 2010-02-02

Prep for 3.0.STABLE23

9878. By Amos Jeffries on 2010-02-01

Author: Frank Schmirler <email address hidden>
Bug 2854: assertion failed: peer_select.cc:627

Peer logging strong omitted from bug 2851 patch port.

9877. By Henrik Nordström on 2010-02-01

pam_auth SQUID_SOLARIS ifdef incomplete

9876. By Henrik Nordström on 2010-02-01

pam_auth in 3.1 is C not C++

9875. By Amos Jeffries <email address hidden> on 2010-02-01

3.1.0.16

9874. By Amos Jeffries on 2010-02-01

Prep for 3.1.0.16

9873. By Amos Jeffries on 2010-02-01

Prep for 3.0.STABLE22

9872. By Amos Jeffries on 2010-01-31

Author: Marko <email address hidden>
Bug 2496: Downloading some variants in full before relaying

AKA, assertion failed: comm.cc:115: "ccb->active == false"
if the client disconnected before download finished arriving.

9871. By Amos Jeffries on 2010-01-31

Author: Graham Keeling <email address hidden>
WCCPv1 not connecting to router correctly

I am coming across a problem with WCCPv1...

squid-2.5 connects to UDP port 2048, I get replies, and everything else then works.

squid-3.1 looks like it is trying to connect to UDP port 0 on the cisco.
[and fails to work]

I have looked at the src/wccp.c for squid-2.5, and it is clear that the port is
being set to 2048 for the connection to the router.
I have also looked at the source for 2.6, 2.7 and 3.0 (src/wccp.cc for this
version).
In all those, it appears to be setting the port on the outgoing connection.

However, in the 3.1 source, it doesn't.