Hi @Vijay Dhasnamoorthy,

UltimatePDF uses a Chromium-based rendering engine to convert an HTML screen into PDF. The layout logic for header, main content, and footer spacing relies heavily on: 

• CSS margin calculations 
• Runtime measurement of header/footer height 
• Injected JavaScript used internally by the component to compute offsets 

When Content Security Policy (CSP) is enabled at the environment level, one or more of these internal mechanisms can be blocked. 

This causes: 

• Header/footer height to be calculated as 0 or auto 
• Main content to start at the top of the page 
• Result: content overlaps header/footer

From UltimatePDF’s own implementation and documentation: 

• It injects inline styles and scripts during rendering 
• It relies on runtime DOM measurement 
• CSP policies that block: 
  • unsafe-inline styles 
  • unsafe-inline scripts 
  • blob: or data: sources 
    will silently break layout calculations

Recommended resolution

Update CSP to allow inline styles:

HTTPstyle-src 'self' 'unsafe-inline';

• This is commonly sufficient
• Low security risk (styles only)
• Resolves header/footer overlap in most cases

Hope this helps,

Cheers.

Saugat