Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

REST API returns 501 Not Implemented Error Until Page is Visited Edited

Our app has some minor differences between Confluence Server and Confluence Cloud (such as minor macro storage format differences and data being moved out of page attachments to our servers). We created an automated tool to go through all Confluence Cloud spaces and update our macros as well as grab attachments using the REST API. The problem is we see issues with some, but not all, REST API calls after users have run the Atlassian Cloud Migration Assistant and are running our automated tool in Confluence Cloud. 

Our REST API calls to GET /rest/api/content/<page-id>, GET /rest/api/content/<page-d>/child/attachment and GET /download/attachments/<attachment> all work successfully. A call to  PUT /rest/api/content/<page-id> however fails with a "HTTP/1.1 501 Not Implemented" response.  The PUT call continues to fail even if run multiple times. The only way for the PUT call to succeed is to have a user manually view the Confluence Cloud page.  Since users may have thousands of inserted macros on their Confluence Cloud instance this can be a major pain for them to have to manually visit every page before running our migration tool.

Why is the PUT operation failing with a "501 Not Implemented" until a user visits a page converted from Confluence Server to Confluence Cloud? Is there any workaround we can use to force whatever change happens when a user first visits the page and thus allow our PUT call to work?

1 answer

1 accepted

1 vote
Answer accepted

This was solved by appending "?status=current" to the URL when performing the PUT request to update the page: "/wiki/rest/api/content/PAGE_ID?status=current"

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Atlassian Cloud Migration

Cloud migration resources roundup: June 2021

...ustomers receive an estimated 155% ROI and total benefits/savings of $1.8M over three years! Check out the report and the rest of our newest resources below, as well as our tried and true that m...

129 views 0 9
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you