This may be more of an HTTPUpload issue (I use Openfire), but it slightly mangles the filename when pushed to HTTPUPload via File Share, IF the file name has white spaces in it.
As a result, the link presented to the chat window is "http://<server>/httpfileupload/<uuid>/<firsthalffilename>" <nameafterspace>, with only the quoted portion acting as a URL (which also matches the file that has been uploaded).
I realize that HTTP and filename-spaces don't mix will -- but perhaps it's better to substitute %20 for the white space before push, but it also might be server-side.
This may be more of an HTTPUpload issue (I use Openfire), but it slightly mangles the filename when pushed to HTTPUPload via File Share, IF the file name has white spaces in it.
As a result, the link presented to the chat window is
"http://<server>/httpfileupload/<uuid>/<firsthalffilename>" <nameafterspace>
, with only the quoted portion acting as a URL (which also matches the file that has been uploaded).I realize that HTTP and filename-spaces don't mix will -- but perhaps it's better to substitute %20 for the white space before push, but it also might be server-side.