REST API returns errant space char at end of root page ID value

[David Bakkers]

I've found what I think might be a bug in Confluence Servers v6.9.0 and 6.3.4

When you use the REST API to query the root page to get its ID (using a GET to the URL https://{MyServer}/rest/api/space/{SpaceKey}/content/page?depth=root ) the value returned for the id has an errant extra space after the numerical value. IE, if the root page's id is 12345678, as shown via the Page Information page, the value returned by the API is "12345678 "

That extra character needs to be removed if the id number is to be used in subsequent REST API queries to create pages with the root as the ancestor.

Can anyone else confirm this issue?

[David Bakkers]

Hmmm. It seems to be an issue with the environment I'm using to submit the REST API calls.

I'm using PowerShell and the Invoke-RestMethod applet to handle parsing all the JSON, but when I make the same call to the API using other REST tools and methods, the errant space doesn't seem to be there.

I've just done some more testing and decoded the errant character to its ASCII value, and it comes back as 32, so it's definitely a space.

What's weird is that I use Invoke-RestMethod to interact with the REST API of both Jira and Confluence for lots of other things and no other returned value has this issue. It seems to be some issue with how Confluence is encoding the response in UTF8.

[David Bakkers]

I'm going to raise this as a bug with the Atlassian devs and see if they can advise of the cause.