Author: kbraak@gbif.org
Created: 2015-09-16 12:52:32.317
Updated: 2015-09-16 12:52:32.317
Parameters in the request can be UTF-8 encoded when using Tomcat by adjusting Tomcat's Connector configuration as explained here: https://struts.apache.org/docs/how-to-support-utf-8-uriencoding-with-tomcat.html
To test, I added URIEncoding="UTF-8" to Tomcat's configuration on UAT, and restarted Tomcat. Evidently this solved the problem with Species search, e.g. http://www.gbif-uat.org/species/search?q=bl%C3%A5b%C3%A6r&dataset_key=d7dddbf4-2cf0-4f39-9b2a-bb099caae36c
I recommend this configuration change also be done to the Dev and Production Tomcat instances. The next time we upgrade Tomcat, will we have to apply this change manually or is there a way to script it [~cvizitiu@gbif.org]?
Unfortunately it doesn't fix the bad common name shown on http://www.gbif.org/species/4164146 Apparently it came in badly encoded, which can be seen by looking at the verbatim record, http://www.gbif.org/species/101354396/verbatim
Author: cvizitiu@gbif.org
Comment: No script AFAIK; will have to do it manual it would seem.
Created: 2015-09-16 15:17:52.287
Updated: 2015-09-16 15:17:52.287
Author: kbraak@gbif.org
Created: 2015-09-16 17:04:24.688
Updated: 2015-09-16 17:04:24.688
Thanks Cip.
[~omeyn@gbif.org] I'll put this Tomcat configuration change on your radar, for the next time we redeploy the portal. Thanks.
Author: mdoering@gbif.org
Comment: added to prod server.xml too without a restart
Created: 2015-09-16 17:17:00.825
Updated: 2015-09-16 17:17:00.825
