Confluence REST v1 Search Endpoint FAILS - Cursor of next URL is EXTRAORDINARILY long, leading to 413 error

Confluence Development Confluence Cloud
, ,
1

This started happening after Sept 4, 2025, around 2 PM.

Running the following CQL search returns results with a reeeeeeeeeeeaally long next URL:

/wiki/rest/api/content/search?cql=type=page&limit=200

image
image1930×789 169 KB

(Note: in the screenshot I called the endpoint with an additional expand query parameter. But I checked, it makes no difference.)

The cursorquery param is 10981 characters long. Calling this massive next URL is not being liked by CloudFront:

413 ERROR

The request could not be satisfied.

Bad request. We can’t connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.
If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.

Generated by cloudfront (CloudFront)
Request ID: h1PZRrF3xufbBG5CBNXixYBFA-LQhJyFzgu_V4Q_YIrAJvbcsuP8VA==

The length seems to increase with the limit. Setting a limit of 100 (instead of 200) decreases the cursor to 5521 characters.

Smells like bug? Can anybody confirm this? Tested on 2 sites, both show that behavior.

1 Like
2

Confirmed we saw this on our development environment yesterday too. I’m guessing some sort of concatenation bug as the cursor has a repeating pattern.

1 Like
3

we also started experiencing these issues over the weekend.
is there an official bug report we can follow up on?

4

@Chris_at_DigitalRose You are right! Repeating pattern

image
image1897×467 113 KB

5

Bumped into this issue as well, this is a joke. Opened an ECOHELP issue with Critical level, got some response but no official solution or confirmation yet.

6

My ticket has been escalated to the endpoint owner, thus confirming an issue on their end.

3 Likes
7

We identified that a change in one of the flags recently enabled on our side caused this problem. After disabling it, we internally confirmed that the long cursor does not happen anymore, even if the query parameter limit is set to a large number.

Could you guys please check as well?

Update: our app is working well now.

8

Looks good again. Thanks for going the ticket-route!

1 Like