Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Don't expose InitList and PrintList tag communication to Web Request

Components

Labels

Description

Plan:

  1. add "nameToSpecialMapping" tag processor class property

  2. use it instead of "NamesToSpecialMapping" request variable

  3. no need to create sub-array for each prefix, because value of "nameToSpecialMapping" is unique to each unit and therefore to each prefix

Context Information

None

Additional information (do not use)

None

Activity

Alex November 28, 2016 at 9:26 AM

Closing issues of a released version.

[API] Administrator January 17, 2016 at 12:18 PM

User committed a fix to 5.2.x. Commit Message:

Fixes - Don't expose InitList and PrintList tag communication to Web Request

Differential Revision: http://qa.in-portal.org/D175

Alex January 17, 2016 at 12:18 PM

alex closed D175: - Don't expose InitList and PrintList tag communication to Web Request by committing rINP16314: Fixes - Don't expose InitList and PrintList tag communication to Web….
alex updated the diff for D175: - Don't expose InitList and PrintList tag communication to Web Request.

Gleb Sinkovskiy December 9, 2015 at 8:16 AM

glebs accepted D175: - Don't expose InitList and PrintList tag communication to Web Request.
D175: - Don't expose InitList and PrintList tag communication to Web Request is now accepted and ready to land.

http://qa.in-portal.org/D175

Alex December 6, 2015 at 2:36 PM

alex added a dependent revision for D175: - Don't expose InitList and PrintList tag communication to Web Request: D180: - Do not use "Web Request" and "Session" concepts in CLI.

http://qa.in-portal.org/D175

Fixed

Details

Priority

Assignee

Reporter

Developer

Reviewer

Change Log Group

Fixed

Change Log Message

Patch Instructions

Patches must be submitted through Phabricator.

Story Points

Fix versions

Created December 5, 2015 at 2:02 PM
Updated December 29, 2024 at 11:26 PM
Resolved January 17, 2016 at 12:18 PM