[RTFACT-17349] Tomcat version 8.5.x and up doesn't support special characters Created: 19/Aug/18  Updated: 05/Dec/18  Resolved: 06/Sep/18

Status: Resolved
Project: Artifactory Binary Repository
Component/s: Tomcat
Affects Version/s: 6.2.0
Fix Version/s: 6.3.2

Type: Bug Priority: Critical
Reporter: Batel Tova Assignee: Tamir Hadad
Resolution: Fixed Votes: 2
Labels: None

Issue Links:
duplicates RTFACT-17334 Retrieve Latest Artifact REST API is ... Resolved
Assigned QA: Maria Pogozelits
Sprint: Leap 34


Currently, the retrieve latest artifact REST API doesn't work because of the tomcat version that blocking special characters by default.

As a workaround in order to support the special characters we need to modify the tomcat.conf as the following :

<Connector port="8081" sendReasonPhrase="true" relaxedPathChars='[]' relaxedQueryChars='[]'/>

As mentioned here  " To prevent Tomcat rejecting such requests, this attribute may be used to specify the additional characters to allow. If not specified, no addtional characters will be allowed. The value may be any combination of the following characters: {{" < > [ \ ] ^ ` { | }}} . Any other characters present in the value will be ignored." 


Comment by Chris Zardis [ 22/Aug/18 ]

Think there needs to be an 'affects version' on this bug so that users can see which versions of Artifactory (by default) have this issue

Comment by Alexander Stipsits [ 10/Sep/18 ]

Is this really resolved?

We're running Artifactory 6.3.3 and also have the problem that https://www.jfrog.com/confluence/display/RTF/Artifactory+REST+API#ArtifactoryRESTAPI-RetrieveLatestArtifact is not working because it is returning a 400 error code.

Comment by Alexander Stipsits [ 10/Sep/18 ]

Forget my previous comment. I found the problem on our side. We've overridden the server.xml with an old version.

Generated at Thu Nov 21 06:18:33 UTC 2019 using JIRA 7.6.16#76018-sha1:9ed376192612a49536ac834c64177a0fed6290f5.