This is not a WorldServer specific issue, but rather a Tomcat update issue. In tomcat 7 the default encoding is ISO-8859-1 and in tomcat 8 it is UTF-8.
The issue is fixed permanently in WorldServer 11.3.3.
There are 3 workarounds for earlier versions:
1- recreate the project avoiding special characters in the project and/or file name
2- change tomcat's
server.xml file. Add
URIEncoding="ISO-8859-1" as follows (make sure you restart
WorldServer after this change)
:
<Connector port="8080" protocol="HTTP/1.1"
connectionTimeout="20000"
redirectPort="8443"
URIEncoding="ISO-8859-1"/>
If you are using the S
SL protocol, make sure to add it to the corresponding connector as well, where the port can be either 443 or the default tomcat 8443. Here is an example:
<Connector
protocol="org.apache.coyote.http11.Http11NioProtocol"
port="443" maxThreads="200"
URIEncoding="ISO-8859-1"
scheme="https" secure="true" SSLEnabled="true"
keystoreFile="C:\keystore\ssl-sdl-test-2018-2019.pfx" keystorePass="nopasswd"
clientAuth="false" sslProtocol="TLS"/>
3- or set the strict servlet complicance property. See reference
page on the Tomcat Apache page.
The server.xml file can be found on the server where WorldServer is installed (application server) and under this directory:
<WS_Home>\ tomcat\conf\ server.xml
If you are working in a clustered environment, the change in the server.xml file should be applied to the servers where tomcat is running.
Alternatively, the workaround to be able to download file despite the error using is to follow these steps:
-
find the file in the target folder in Explorer
-
right click on the target folder (not on the file) and select Download
-
the download of the whole target folder will start. Per default, WorldServer will create a zip file called assets.zip. You can rename it as you prefer.
-
save the zip file locally. It will contain your target file.
