[Upgrade to Bubble version 32] Improved redirect handling in API Connector

Announcements New features
1

Hi everyone,

My name is Nick, and I’m a product manager on the editor team. Today we’re releasing Bubble Version 32, which includes an update to how the API Connector handles HTTP redirects.

When an API endpoint returns a redirect (like a 301, 302, or 303), the HTTP standard expects the client to follow that redirect using a GET request — regardless of the original method. For example, if your app sends a POST to an endpoint and receives a 302 redirect, the follow-up request to the new URL should be a GET. The exception is a 307 redirect, which explicitly tells the client to preserve the original method (e.g., keep it as a POST).

In previous versions:

  • API Connector requests would preserve the original HTTP method when following redirects. This caused issues when endpoints expected the request to switch to GET — (e.g., 301, 302, 303).

With this update:

  • The API Connector now follows non-307 redirects using GET. This aligns with standard HTTP redirect behavior. 307 redirects will continue to preserve the original HTTP method (POST), as expected.

What this means for you:

For most apps, this change will resolve redirect-related issues and require no action.

If your API calls intentionally rely on redirects that preserve the original method (e.g., a POST that redirects and should remain a POST), you should review those calls after upgrading.

You can upgrade to version 32 in Settings > Versions.

As always, we welcome your feedback. Thanks for building on Bubble!

Nick

10 Likes
2

Thanks @nick.carroll. I’m still on Version 30. A couple of questions since this isn’t documented very well:

  1. If I upgrade to Version 32, will it also include 31?
  2. If I don’t upgrade manually, will my app eventually be upgraded at some future date?
3

Hi Nick, this is a good news. However, could you also consider adding a no follow redirect option? There’s already a request for that on Ideaboard.

2 Likes
4

Great questions!

  1. Yes, if you update to version 32, it will include 31. There is no ability to cherry pick bubble versions, unfortunately
  2. No, we won’t force upgrade your versions. If we ever needed to do so for whatever reason, we would give an adequate heads up.
1 Like
5

Noted!

2 Likes
6

OK, thank you!

7

Hi @nick.carroll I’m not very technical, but how do we know in real life whether our application will have a real impact? Are there any benchmarks or tests we can do to see if everything is working properly without having to go through hundreds of APIs?

2 Likes