Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)
Normally, JID instances are stringprepped (ensuring that they conform to a specific form and format). This mechanism is resource intensive. It can be skipped, if the JID value is supplied by a source that is known to have already applied stringprepped.
Openfire currently assumes that stanzas that arrive from other servers (through S2S) are already stringprepped. This obviously should be the case, but there is far from a guarantee that this has indeed happened.
Openfire should not skip prepping JID values that arrive from remote servers.
Normally, JID instances are stringprepped (ensuring that they conform to a specific form and format). This mechanism is resource intensive. It can be skipped, if the JID value is supplied by a source that is known to have already applied stringprepped.
Openfire currently assumes that stanzas that arrive from other servers (through S2S) are already stringprepped. This obviously should be the case, but there is far from a guarantee that this has indeed happened.
Openfire should not skip prepping JID values that arrive from remote servers.