Bug 23451 – Squid3-ICAP-Support in univention-proxy-Templates abbilden

Bug 23451 - Squid3-ICAP-Support in univention-proxy-Templates abbilden


Summary:	Squid3-ICAP-Support in univention-proxy-Templates abbilden

Status:	CLOSED INVALID

Product:	UCS
Classification:	Unclassified
Component:	Squid
Version:	UCS 3.0
Hardware:	Other Linux

Importance:	P5 enhancement (vote)
Target Milestone:	UCS 3.2-1-errata
Assigned To:	Felix Botner
QA Contact:	Arvid Requate

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2011-08-29 16:53 CEST by Moritz Muehlenhoff
Modified:	2014-04-22 06:52 CEST (History)
CC List:	1 user (show)

See Also:
What kind of report is it?:	---
What type of bug is this?:	---
Who will be affected by this bug?:	---
How will those affected feel about the bug?:	---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Moritz Muehlenhoff

2011-08-29 16:53:43 CEST

ICAP ist ein Protokoll zur Anbindung externer Content-Scanner (z.B. Virenscanner etc.). Squid unterstützt ab Version 3 (und somit in UCS 3.0) auch ICAP, die Templates für univention-squid aus UCS 3.0 werden aber erstmal nur die bestehenden UCR-Variablen aus UCS 2.4 abbilden.

Die entsprechenden ICAP-Optionen könnten später in die Templates integriert werden.

Comment 1 Felix Botner

2014-03-03 15:25:16 CET

Such special configurations can be done in /etc/squid3/local.conf (which is automatically included in /etc/squid3/squid.conf).

Comment 2 Arvid Requate

2014-04-07 18:27:32 CEST

Ok.

Comment 3 Stefan Gohmann

2014-04-22 06:52:01 CEST

Nothing to release.