searchPosts returns 403

[rseiffert]

https://public.api.bsky.app/xrpc/app.bsky.feed.searchPosts?q=moss returns a 403 (Forbidden) although the documentation states it should be callable without authentication.

[panda-byte]

Same here. However, I noticed that https://public.api.bsky.app/xrpc/app.bsky.feed.searchposts?q=moss (note the lower-case "posts") works instead now. So maybe the spelling was changed and the API doc wasn't updated? The documented URL did work before up until at least a couple of days ago.

[chadsteele]

thanks guys... needless to say, I've been suffering this for about 3 days wondering why my proxy was failing.
Not cool arbitrary api update guy! ;) ;)

[mary-ext]

AppView is deliberately returning 403 to decrease load at the moment, not because of a naming change.

xrpc-server doing case-insensitive matching smells like a bug to me.

[panda-byte]

I see, thank you for the explanation @mary-ext ! Seems I lucked out with my workaround. All other variations of capitalization also work, so if API users wanted to be cheeky, they could randomize the capitalization to circumvent the block.

Anywys, wouldn't 503 (Service Unavailable) be a more suitable HTTP status code in this case? 4xx are for client errors, 5xx for server errors.

[vyv03354]

AppView is deliberately returning 403 to decrease load at the moment

If so, the search page should not retry every second.

[mary-ext]

this doesn't seem to be an issue anymore

[bnewbold]

Related: bluesky-social/atproto#3844