com.atlassian.confluence.content.render.xhtml.migration.exceptions.UnknownMacroMigrationException: The macro 'next_previous_links' is unknown.
HTTP Status Codes
When REST API requests are sent to carryout various actions, various HTTP status codes will be returned based on the state of the action (success or failure) and the HTTP method (POST, GET, DELETE
) executed. The following are the definitions of the various HTTP status codes that are returned:
Success HTTP status codes
Code | Code Summary | Description |
---|---|---|
100 | Continue | The server has received the request headers, and the client should proceed to send the request body. This is applicable in the case of a request for which a body needs to be sent (e.g., POST request). This interim response is used to inform the client that the initial part of the request has been received and has not yet been rejected by the server. The server will send a final response after the request has been completed. |
200 | Ok | HTTP request was successful. The output corresponding to the HTTP request will be returned. Generally used as a response to a successful GET REST API HTTP method. |
201 | Created | HTTP request was successfully processed and a new resource was created. Generally used as a response to a successful POST REST API HTTP method. |
202 | Accepted | HTTP request was accepted for processing, but the processing has not been completed. |
Error HTTP status codes
Code | Code Summary | Description |
---|---|---|
400 | Bad request | The server cannot or will not process the request due to something that is perceived to be a client error (e.g., malformed request syntax, invalid JSON format). |
401 | Unauthorized | When authentication is required and has failed, or when authentication has not yet been provided. |
406 | Not Acceptable | The requested resource is only capable of generating content not acceptable according to the Accept headers sent in the request. The default accept header is application/json . If you do not specify an accept header, the default accept header is applied. However, if you specify an accept header that is not supported, this status code is displayed. |
415 | Unsupported Media Type | The request entity has a media type that the server or resource does not support. The following are the supported content types: application/json , application/x-www-form-urlencoded and multipart/form-data . If you send a content type that differs to the content type supported, this status code is displayed. |
500 | Internal server error | Server error occurred. |
501 | Not implemented | When the server either does not recognize the request method, or it lacks the ability to fulfill the request. |
com.atlassian.confluence.content.render.xhtml.migration.exceptions.UnknownMacroMigrationException: The macro 'next_previous_links2' is unknown.