tracker issue : CF-4199667

select a category, or use search below
(searches all categories and all time range)
Title:

Update 4 and 5 break Update 3 fix for CFCOOKIE Null values

| View in Tracker

Status/Resolution/Reason: Closed/Fixed/Fixed

Reporter/Name(from Bugbase): Timothy Niswander / Timothy Niswander ()

Created: 09/13/2017

Components: Security, General

Versions: 2016,11.0

Failure Type: Others

Found In Build/Fixed In Build: 303689 / 307122

Priority/Frequency: Normal / Most users will encounter

Locale/System: / Win 2012 Server x64

Vote Count: 0

Listed in the version 2016.0.06.308055 Issues Fixed doc 
Problem Description: Latest Updates breaks prior updates built into 2016 Installer Refresh Update 3

Steps to Reproduce: Install latest CF 2016 Enterprise installer, then install either update 4 or 5 

Actual Result:  NULL / No value CFCOOKIE functionality breaks the fix for this issue in UPDATE 3

Expected Result:  CFCOOKIES with no value will not cause errors in CF 

Any Workarounds:  uninstall update 4 or 5

Attachments:

Comments:

Hi Timothy, Please let us know a couple of things on this issue: 1.The build number of the HF3 update in the admin, where you do not see the issue. 2.The path to HF3,i.e, have you applied HF3 on HF2 or HF1 or GM. Thanks!
Comment by S P.
330 | September 20, 2017 10:47:48 AM GMT
Hello, Here is the version of CF listed in the admin summary: 2016,0,03,301771 It's the latest CF installation download from the Adobe website. All updates prior to HF4 and HF5 are already in that build. After the installation of that packaged build, CF Cookies work as expected. If I apply either of the only hotfixes that are available AFTER the base install, the CF Cookie with null/blank values will then cause the error. I don't have the option to revert to any hot fix prior to what's already in the latest CF installation download. But the issue isn't in that file, it only occurs after I apply the latest hotfixes, 4 or 5 Let me know if you need any more info.
Comment by Timothy N.
331 | September 20, 2017 11:08:55 AM GMT
Hi Timothy, Please check your mail with the instructions for applying the patch for this issue. Thanks!
Comment by S P.
332 | October 13, 2017 05:16:43 AM GMT