You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
zooma-ui uses [ in URL parameters when communicating query settings (source/ontology selections and the like), which is not allowed in modern tomcat instances (all major versions, 7,8,8.5 have been updated to that behaviour). Now there are settings to permit those characters in server.xml, but using those only lets the error messages go away - the webservice however seems to no get the exact sequence of characters it expects and therefore does not function. I have discussed this with @udp and the recommendation is to wait until the frontend is fixed, until then Zooma2 can only be deployed on tomcat versions lower than 7.0.73, 8.0.39, 8.5.7. This issue is only for documentation and wont be directly acted on; we can close it when the new UI is there.
The text was updated successfully, but these errors were encountered:
matentzn
changed the title
Zooma 2 is incompatible with modern tomcat due two unescaped URL characters
Zooma 2 is incompatible with modern tomcat due to unescaped URL characters
Aug 28, 2020
zooma-ui uses
[
in URL parameters when communicating query settings (source/ontology selections and the like), which is not allowed in modern tomcat instances (all major versions, 7,8,8.5 have been updated to that behaviour). Now there are settings to permit those characters in server.xml, but using those only lets the error messages go away - the webservice however seems to no get the exact sequence of characters it expects and therefore does not function. I have discussed this with @udp and the recommendation is to wait until the frontend is fixed, until then Zooma2 can only be deployed on tomcat versions lower than7.0.73, 8.0.39, 8.5.7
. This issue is only for documentation and wont be directly acted on; we can close it when the new UI is there.See also stack overflow.
The text was updated successfully, but these errors were encountered: