When using the Community Edition 2.0.2 and the current audit_osx.sh script, online submission fails due to an invalid XML. Closer inspection showed that the culprit was an ampersand in a volume name, eg:
Manually replacing & with & has no effect, when posting via curl --data-urlencode data@"$xml_file" $url the server still throws an error, though the file passes 3rd party XML validation. Removing the ampersand from the XML works, so the error is definitely limited to that. How should I update the audit_osx.sh script to satisfy the server's requirements for a correct ampersand encoding?
Quick fix. Wherever you see <mount_point> in the script, use CDATA.
I'll add these to the script for the next release.
Awesome, thank you. Quick comment - in my case <mount_point>, <name> and <description>.