Blog Sections Open
Fixing the “Refused to Set Unsafe Header Connection” Manager Bug
What to check when saving a resource leaves the right manager pane blank and the browser console reports an unsafe Connection header.
A resource save that ends with a blank right-hand manager pane is frustrating enough. Seeing the browser console complain about Refused to set unsafe header "Connection" makes it even more confusing.
This is usually a sign that some custom JavaScript or AJAX layer in the manager is trying to force an HTTP header that browsers do not allow scripts to set. The result is a broken refresh cycle after save.
Where the bug usually lives
- custom manager extensions,
- older ManagerManager-related scripts,
- AJAX wrappers that try to pass forbidden headers,
- outdated browser-side code copied from old examples.
The fix is rarely in the resource data itself. It is almost always in the manager-side JavaScript that handles the post-save refresh. Remove the forbidden header logic, retest the save flow, and only then look deeper if the pane still fails to reload.
In short, this is a manager transport problem, not a content problem.
Fixing Ditto and Wayfinder 404s on Nested URLs
Why Ditto and Wayfinder output can start returning 404s when nested URLs are enabled and how to align the routing logic properly.
Fixing Escaped Quotes in JotX Comment Output
Why JotX comments can start showing backslashes before quotes and what to normalize before rendering comment text.