Project

General

Profile

Bug #8096

Special characters not propagated by the config sync engine

Added by Marin Bernard almost 2 years ago. Updated 27 days ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
XMLRPC
Target version:
-
Start date:
11/15/2017
Due date:
% Done:

0%

Estimated time:
Affected Version:
2.4.1
Affected Architecture:
All

Description

Hi,

We use configuration synchronisation between two pfSense boxes to sync a list of firewall aliases and rules. These objects include description strings with special characters (mainly French letters with accents).

On the backup node, those characters are always replaced by a space.

This issue does not exist with the backup/restore feature, which embeds special chars as HTML entities. However, it seems the configuration sync engine is unable to handle them properly on config update.

History

#1 Updated by Jens Groh over 1 year ago

Version 2.4-latest

I'll second this. The description field does not seem to be properly escaped when syncing to the standby node. We also use the field for better sortability and descriptions often inlucding a hostname like host.name.tld and separating infos with a pipe | and/or round brackets (). All these symbols .|() are replaced by spaces on the secondary node so we can not sort on the standby node like on the primary. Please include escaping the description field(s) to support more characters at least like dots . and pipes |

Thanks and kind regards,

Jens

#2 Updated by Jim Pingle 27 days ago

  • Category changed from 62 to XMLRPC

Also available in: Atom PDF