# Unable to remove X-Frame-Options header via ignition.conf (Parameters ignored in wrapper.log) **URL:** \ **Category:** Ignition\ **Created:** [February 10, 2026, 3:06am UTC](https://forum.inductiveautomation.com/t/unable-to-remove-x-frame-options-header-via-ignition-conf-parameters-ignored-in-wrapper-log/113859 "2026-02-10T03:06:13Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![chentaoko](https://avatars.discourse-cdn.com/v4/letter/c/e79b87/32.png) [@chentaoko](https://forum.inductiveautomation.com/u/chentaoko)\ **Post date:** [February 10, 2026, 3:06am UTC](https://forum.inductiveautomation.com/t/unable-to-remove-x-frame-options-header-via-ignition-conf-parameters-ignored-in-wrapper-log/113859/1 "2026-02-10T03:06:13Z")
Hi everyone, I am trying to embed an Ignition WebDev Python Resource (HTML) into **Power BI Desktop** using the HTML Content visual. Currently, the content is being blocked because the response header `X-Frame-Options` is set to `SAMEORIGIN`. I have attempted to remove this header and set the CSP by modifying `ignition.conf`, but the Gateway seems to completely ignore these parameters. **What I have configured in `ignition.conf`:** I added the following lines to the `wrapper.java.additional` section. I ensured the numbering is continuous (my previous line is .9) and there are no commenting `#` characters at the start. wrapper.java.additional.9=-Dedition= wrapper.java.additional.10=-Dignition.http.header.X-Frame-Options= wrapper.java.additional.11=-Dignition.http.header.Content-Security-Policy="frame-ancestors \*" **Troubleshooting Steps Taken:** 1. **Restarted Gateway:** I performed a hard restart via Windows `services.msc` (Restart Service). I also tried using `stop.bat` and `start.bat` with Admin privileges. 2. **Verified Syntax:** Checked for hidden spaces, confirmed no `#` signs, and verified the numbering sequence is unbroken. 3. **Checked Browser:** After restart, Chrome DevTools (Network tab) still shows `X-Frame-Options: SAMEORIGIN`. 4. **Checked `wrapper.log` (CRITICAL ISSUE):** I inspected the `wrapper.log` after the restart. I can see other parameters being loaded, **but the lines for `X-Frame-Options` and `Content-Security-Policy` are completely missing from the log.** It seems the wrapper is not reading these specific lines at all. **My Question:** Why would the Ignition Gateway (or Java Wrapper) ignore valid `wrapper.java.additional` parameters in the config file? Is there a Windows permission issue (like `VirtualStore`) or a caching mechanism that prevents `ignition.conf` changes from being picked up even after a service restart? Any help would be appreciated. I've been stuck on this for days! Thanks. ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [February 10, 2026, 3:32am UTC](https://forum.inductiveautomation.com/t/unable-to-remove-x-frame-options-header-via-ignition-conf-parameters-ignored-in-wrapper-log/113859/2 "2026-02-10T03:32:55Z")
In the manual these system properties use underscores and lowercase: [Gateway and Gateway Network Parameters | Ignition User Manual](https://docs.inductiveautomation.com/docs/8.1/appendix/reference-pages/gateway-configuration-file-reference/gateway-and-gateway-network-parameters#x-frame-options) I’m not sure there’s even a setting for CSP. Where did you get these properties you’re trying to use from? Based on your post I’m guessing the answer is an LLM… ---
**Author:** ![chentaoko](https://avatars.discourse-cdn.com/v4/letter/c/e79b87/32.png) [@chentaoko](https://forum.inductiveautomation.com/u/chentaoko)\ **Post date:** [February 10, 2026, 3:54am UTC](https://forum.inductiveautomation.com/t/unable-to-remove-x-frame-options-header-via-ignition-conf-parameters-ignored-in-wrapper-log/113859/3 "2026-02-10T03:54:15Z")
It seems works, thanks sir. Y r right, the answer comes from Gemini………………..