Problem with app what already disables the x-frame-option?

Mar 12, 2015 at 2:10 PM
Hi all

Seems like the code will throw an exeption if the App has already disabled the x-frame-option. We've been testing peshos poll from the Sharepoint store in an environment where the Ventigrate solution has been installed and activated on the app hosting web application.

Regards, Steen

03/12/2015 14:23:33.58 w3wp.exe (0x46F0) 0x4B9C SharePoint Foundation Runtime tkau Unexpected System.ArgumentException: Item has already been added. Key in dictionary: 'AllowFraming' Key being added: 'AllowFraming' at System.Collections.Hashtable.Insert(Object key, Object nvalue, Boolean add) at Ventigrate.Shared.PermissiveXFrameHeader.Modules.PermissiveXFrameHeaderModule.context_BeginRequest(Object sender, EventArgs e) at System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) 4505f29c-f2e4-a074-dcd4-597da0b51455
03/12/2015 14:23:33.58 w3wp.exe (0x46F0) 0x4B9C SharePoint Foundation General ajlz0 High Getting Error Message for Exception System.ArgumentException: Item has already been added. Key in dictionary: 'AllowFraming' Key being added: 'AllowFraming' at System.Collections.Hashtable.Insert(Object key, Object nvalue, Boolean add) at Ventigrate.Shared.PermissiveXFrameHeader.Modules.PermissiveXFrameHeaderModule.context_BeginRequest(Object sender, EventArgs e) at System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) 4505f29c-f2e4-a074-dcd4-597da0b51455
03/12/2015 14:23:33.58 w3wp.exe (0x46F0) 0x4B9C SharePoint Foundation General aat87 Monitorable 4505f29c-f2e4-a074-dcd4-597da0b51455
Coordinator
Mar 12, 2015 at 2:25 PM
Edited Mar 12, 2015 at 2:26 PM
Hi,

I can confirm this is a bug. I'll fix it asap.

Kind regards,
Coordinator
Mar 16, 2015 at 12:12 PM
Hi,

The bug has been fixed and you can download the newest deploypackage and update your solution.

Kind regards,
Steven
Marked as answer by vandest on 3/16/2015 at 5:12 AM