Uploading wiki markup mangles URLs with parameters - converting & to &

Joel Morris January 8, 2022

I'm using REST to upload wiki content to my Confluence server (v7.5.2).

'body': { 'storage': { 'representation': 'wiki', 'value': body } }

Where my data has some wiki markup, including something like this:

[ Click here | https://server/Create!init.jspa?pid=123&param1=abc&param2=14 ]

which Confluence then turns into:

[ Click here | https://server/Create!init.jspa?pid=123&param1=abc&param2=14 ]

Is there a way to escape the & in my source so that Confluence will keep the URL intact?

6 answers

1 vote
Pramodh M
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
January 8, 2022

Hi @Joel Morris 

Welcome to the Community!!

Wherever the Special Characters are there, you can include HTML URL Encoding Ref

https://www.w3schools.com/tags/ref_urlencode.ASP

So if you include %26 API should not return error and your URL will also work fine

Please let me know if it works for you!!

Thanks,
Pramodh

0 votes
Joel Morris January 9, 2022

@Pramodh M am I misinterpreting your solution?

0 votes
Joel Morris January 8, 2022

Jira CreateIssueDetails!init.jspa appears to actually need the & character between the key=value pairs.

0 votes
Pramodh M
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
January 8, 2022

Hi @Joel Morris 

Use

& in place of &

It should work!!

Thanks,
Pramodh

0 votes
Joel Morris January 8, 2022

Thanks @Pramodh M !  

It certainly looks right in Confluence now!  But the link still doesn't do what I expect in JIRA.

https://jiraserver/secure/CreateIssueDetails!init.jspa?pid=1234%26reporter=morris

Jira gives the error "You have not selected a valid project to create an issue in."

But if I change that %26 to an & in my browser's address bar, then Jira behaves correctly.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events