Server Side Redirects

I am trying to implement page load redirects on the server side, since bubble security scans have flagged my redirects on page load as NOT being secure.

But no matter what I do, even if I create a redirect on a brand new page on a test app with no other workflows but the “on page load-go to index workflow” it does not behave properly.

I am using a redirect checker to test (as demonstrated on a video tutorial) and I always get a 200 ok.

I have followed the bubble manual too, but it does not seem to work for me.

Does anyone know the secret to get these to work properly?

Use something like current user is logged in, I think. There’s a forum post and in manual states what sort of conditions will force server side redirect.

Thanks, I followed the manual’s suggestion on a blank page, and it still won’t server side redirect.

Here is the workflow, which as far as I can tell conforms to the manual’s spec. It redirects, but not server side.

These sound like 2 different issues. Or are you saying that a brand new page with

is still flagging as an issue?

Yes, brand new page with the above workflow, when I check it in redirect-checker.org, does not show as a server side redirect, which would be a 301 or 302 I believe.

I get a 200 ok response, which means the page is loading, and THEN the redirect occurs.

It was not working for me when flagged on an app I made, so I tried it on my simple test-app with a new blank page.

I was always under the assumption that any calls to a Bubble app still pings an app page first then resolves (server-side) if a user should be redirected. :thinking:

Can you point to the part of the manual that says otherwise?

Well the manual on this topic is lacking IMHO, it just says, do this and that and it will be server side. But there is no way to know its working. Except that if you check it with a checker, or also in my case Flusk flags it no matter what I try.

It works for this Airdev guy in this video, but I cannot get it to behave the same. https://www.youtube.com/watch?v=6zIPbCDMkC4

Here is what the error looks like in Flux, which does appear to point to the same problem, pinging the page if properly set up should NOT return a 200. I just cannot figure out how to make it work. Even on the simplest of setups, a page with nothing but 1 redirect workflow.

This thread has insights into server side redirects and links to other posts that link to other posts that link to articles…a good thread to pull on to get started on uncovering why it is not working

send the editor link and i’ll show you what to do

Have you tried using the “User is logged out” (or something to that effect) event instead of on Page Load event + Current user is logged out.

1 Like

Yes, I have tried the event “User is logged out” as the manual suggests. It redirects, but not server side as far as I can tell.

I have now implemented a suggestion from a thread linked to a thread suggested above, which seems to fix the issue in at least one of my apps: When creating the Go to Page workflow, the Data to send needs to be left blank.

This I did not see mentioned in the documentation, but found it in the forum.

2 Likes

Ahh okay. That makes sense. Glad you figured it out!