-
Bug
-
Resolution: Fixed
-
Low
-
1000.718.1, 6.3.15, 6.4, 10.3.4
-
6.03
-
20
-
Severity 3 - Minor
-
11
-
-
NOTE: This bug report is for JIRA Server. Using JIRA Cloud? See the corresponding bug report.
Actual Results:
Looking into the application log we can see %20 character (space) was converted to %2520 hence failing the call.
[atlassian.webhooks.plugin.PublishTaskFactoryImpl$PublishTaskImpl] Client error - when posting to web hook at 'http://sample.com/executions?argString=-sshPassword1%2520password&user_id=admin&user_key=admin'
Expected Results:
JIRA should calls the exact URL that has been used to created the WebHook like the one below.
http://sample.com/executions?argString=-sshPassword1%20password&user_id=admin&user_key=admin'
Steps to reproduce:
- Create a new WebHook using the test URL: http://sample.com/executions?argString=-sshPassword1%20password
Workaround:
For customers using Jira 10.3.5 LTS and higher, or Jira 10.6.0 and higher (note: not 10.4.x or 10.5.x), you can activate the fix by enabling the system property:
plugin.webhooks.skip.url.reencoding=true
This property is automatically enabled starting from Jira 10.7.0.
- relates to
-
JRASERVER-78312 Jira 10 forcibly decodes encoded ASCII characters in webhook URLs
-
- Closed
-
-
JRACLOUD-67484 Webhook calls fail if destination URL contains special characters
-
- Closed
-
-
JRACLOUD-42579 WebHook convert the space character %20 into %2520 thus failing the call.
-
- Gathering Impact
-
- is resolved by
-
WILDT-8 Loading...
- mentioned in
-
Page Loading...