Unable to push configuration to Prisma Access instances with commit error "value Node can be at most 512 characters, but current length: XXX value"
368
Created On 01/17/24 03:12 AM - Last Modified 10/21/25 22:30 PM
Symptom
Unable to push configuration to Prisma Access instances with commit error "value Node can be at most 512 characters, but current length: XXX value".
Added multiple domains to the value of "HTTP Header Insertion". This will cause a character limit hit of 512 characters.
Example of the push configuration error (Commit All error) are as follows:
Details: . Validation Error: . vsys -> vsys2 -> profiles -> url-filtering -> example-url-filtering -> http-header-insertion -> example-O365 -> type -> Microsoft Office365 Tenant Restrictions -> headers -> header-0 -> value Node can be at most 512 characters, but current length: 519 value: example.com, example2.com, example3.com, example4.com ... . vsys -> vsys2 -> profiles -> url-filtering -> example-url-filtering -> http-header-insertion -> example-O365 -> type -> Microsoft Office365 Tenant Restrictions -> headers -> header-0 -> value is invalid . Commit failed
Environment
- Panorama
- PANOS-10.2.4
- Prisma Access
Cause
There is a limit of 512 characters per "HTTP Header Insertion" value.
Resolution
- You cannot increase the character limit above 512 character.
- You can only create a new "HTTP Header Insertion" object and add the additional domain names in this new object.
Navigate: Object > Security Profiles > URL Filtering > [URL Filtering Object Name] > HTTP Header Insertion > [HTTP Header Insertion Object Name] > Headers > Values
- Once the remaining domain names are added to the new "HTTP Header Insertion" object, push the configuration to Prisma Access.
Additional Information
None.