#belltyler

1 messages ยท Page 1 of 1 (latest)

cinder finchBOT
frail flame
#

Hello ๐Ÿ‘‹
I've not seen this happen before either. Let me look around..

terse hound
#

Awesome thank you!

tall rampart
#

You don't happen to have that Checkout Session ID in text do you?

#

Or could you transcribe it from the screenshot so I can take a look at it?

#

Hmm this is strange

#

How are you redirecting to Checkout?

left flicker
tall rampart
#

Interesting let me take a look

#

So yeah that looks promising

#

You shouldn't need to pass along cookies from the cache key so that would likely be the first thing to try.

terse hound
#

@tall rampart unfortunately I don't have the session id in text. You'll also notice that it appears that the session ID is super long in the screenshot and is cut off.

We are redirecting to the checkout client side, so.... window.location.href = CHECKOUT_URL

tall rampart
#

Are you using AWS?

#

I think @left flicker's comment above is a good lead

#

Recommend reading through that SO

terse hound
#

Our backend API is on AWS yes. However, the API is only responsible for creating the checkout session. It returns the checkout URL to our frontend (not on AWS) which then redirects the user directly the checkout via window.location.href

The error is coming directly from Stripe at the checkout page URL ๐Ÿค”

The stackoverflow user had that issue when his website not loading.

tall rampart
#

Right but you are sending headers when you redirect

#

It is interesting that you redirect using window.location.href and get this though as opposed to actually redirecting from your backend.

terse hound
#

gotcha... Yeah we built it that way because our service is installed on our users websites via a script

tall rampart
#

Actually based on the SO it still makes sense

terse hound
#

So it seems like this user just really likes cookies.

tall rampart
#

This seems to be specific to AWS and the cookies that using that hosting service initialize

#

Which are then passed on when you redirect

#

So I think suppressing those cookies is the correct thing to do as a first attempt to fix this.

terse hound
#

okay I'll give it a shot.

#

Thanks for the help.