Back to bug 794468

Who When What Removed Added
mark yarborough 2012-02-28 16:39:06 UTC CC epp-bugs
Thomas Heute 2012-04-03 07:21:47 UTC Type Bug Feature Request
CC theute
Component unspecified Portal
hfnukal 2012-08-16 11:16:28 UTC CC hfnukal
Component Portal Portal
Version 5.2.1.GA unspecified
Product JBoss Enterprise Portal Platform 5 JBoss Enterprise Portal Platform 6
Jiri Pallich 2013-11-12 15:05:48 UTC CC jpallich
Divya Mehra 2013-12-17 15:29:33 UTC CC dmehra
Thomas Heute 2013-12-18 09:51:15 UTC Target Release --- 6.2.0
Boleslaw Dawidowicz 2014-01-09 10:36:22 UTC Status NEW ASSIGNED
CC bdawidow
Assignee jbpapp-maint jcosta
Juraci Paixão Kröhling 2014-01-10 17:10:17 UTC Link ID JBoss Issue Tracker GTNPORTAL-3363
Peter Palaga 2014-01-15 15:56:33 UTC Status ASSIGNED POST
CC ppalaga
Jared MORGAN 2014-03-04 03:55:22 UTC Blocks 1072147
Peter Palaga 2014-06-21 10:44:56 UTC CC vramik
QA Contact vramik
Status POST MODIFIED
Target Milestone --- ER04
hfnukal 2014-07-01 13:34:33 UTC Status MODIFIED ON_QA
Jared MORGAN 2014-07-04 02:57:20 UTC Status ON_QA VERIFIED
Doc Text Previously, if a gadget tried to use a proxy URL which was not whitelisted, the gadget would silently fail. In many cases, a log message was not recorded for the failure. This could have resulted in customers incorrectly assuming the gadget contained a bug instead of the actual reason of the gadget using an unauthorized proxy connection. The fix introduces an INFO level log entry describing the root cause of the failure, which corrects the issue.
Jared MORGAN 2014-07-22 00:18:24 UTC Doc Text Previously, if a gadget tried to use a proxy URL which was not whitelisted, the gadget would silently fail. In many cases, a log message was not recorded for the failure. This could have resulted in customers incorrectly assuming the gadget contained a bug instead of the actual reason of the gadget using an unauthorized proxy connection. The fix introduces an INFO level log entry describing the root cause of the failure, which corrects the issue. Previously, if a gadget tried to use a proxy URL which was not whitelisted, the gadget would silently fail. In many cases, a log message was not recorded for the failure. This could have resulted in customers incorrectly assuming the gadget contained a bug instead of the actual reason of the gadget using an unauthorized proxy connection. The enhancement introduces an INFO level log entry describing the root cause of the failure.
Doc Type Bug Fix Enhancement
PnT Account Manager 2018-01-30 01:42:06 UTC CC dmehra
PnT Account Manager 2018-02-06 19:18:41 UTC CC hfnukal
Red Hat Bugzilla 2021-11-14 22:29:42 UTC Assignee jcosta nobody

Back to bug 794468