Bug 40409 – Manual 4.1: Configuring proxy.pac by UCR

Bug 40409 - Manual 4.1: Configuring proxy.pac by UCR


Summary:	Manual 4.1: Configuring proxy.pac by UCR

Status:	CLOSED WONTFIX

Product:	UCS@school
Classification:	Unclassified
Component:	Documentation
Version:	UCS@school 4.1
Hardware:	Other Linux

Importance:	P5 enhancement (vote)
Target Milestone:	UCS@school 4.1.x
Assigned To:	UCS@school maintainers
QA Contact:

URL:
Keywords:

Depends on:	35219
Blocks:
	Show dependency tree / graph

Reported:	2016-01-11 11:42 CET by Sönke Schwardt-Krummrich
Modified:	2023-06-12 15:39 CEST (History)
CC List:	0 users

See Also:
What kind of report is it?:	Bug Report
What type of bug is this?:	1: Cosmetic issue or missing function but workaround exists
Who will be affected by this bug?:	1: Will affect a very few installed domains
How will those affected feel about the bug?:	1: Nuisance – not a big deal but noticeable
User Pain:	0.006
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 Sönke Schwardt-Krummrich

2016-01-11 11:42:56 CET

The new UCR variables introduced with bug 40403 resp. 35219 have to be documented in UCS@school manual.

+++ This bug was initially created as a clone of Bug #35219 +++

At the moment, if you want to exclude sites from going through the proxy, you have to edit /var/www/proxy.pac by hand. It would be an asset, if the proxy.pac file is configurable by UCR Variables.

Comment 1 Florian Best

2017-06-28 14:56:53 CEST

There is a Customer ID set so I set the flag "School Customer affected".

Comment 2 Sönke Schwardt-Krummrich

2019-02-05 21:16:28 CET

This issue has been filled against UCS@school 4.1 (R2). The maintenance with bug 
and security fixes for UCS@school 4.1 (R2) has ended on 5th of April 2018.

Customers still on UCS 4.1 are encouraged to update to UCS 4.3 (or later). 
Please contact your partner or Univention for any questions.

If this issue still occurs in newer UCS versions, please use "Clone this bug"
or simply reopen the issue. In this case please provide detailed information on
how this issue is affecting you.