I have a server set up to work with AD. The LDAP query has an
ampersand in it. When written to openfire.xml, it is correctly written
out as &. When
rerunning the LDAP setup, this gets escaped again into
&amp; and breaks LDAP when the
server is restarted.
Is this a known thing with known scenarios that I should avoid or is this just a random bug?
enough, you can see the same kind of effect when posting a discussion
in rich text, then switching back and forth to preview.
&amp; gets repeatedly escaped into &