-
Notifications
You must be signed in to change notification settings - Fork 81
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: change default api url value #354
Conversation
When using any node version above 16, the cookie was not being persisted across browser refreshes. Changing "http://localhost:1337" -> "http://127.0.0.1:1337" fixed this issue. Refer to this issue: #229
✅ Live Preview ready!
|
I'm so sorry it took so long to merge, thank you! 😊 |
As a note, when using an oauth provider, this does imply changing the Callback URL and setting the |
Thanks. I think ppl would know to do that, I may be wrong tho.. |
I tried quickly to do it on a Strapi 3 API but didn't managed to changed the |
Hey. I changed the host already to 127.0.0.1, because my cookies were getting cleared, but the issue persists. The URL is getting overwritten, then rewritten back from localhost to 127.0.0.1 Video: https://share.cleanshot.com/JphHZDtB Also got a hydration mismatch. |
This reverts commit 4901cdd.
Reverted this in favor of: 93b8bb8 |
Good going 👍🏽 |
@BayBreezy Have you tried it? Does it work for you? |
Not yet lol. |
@benjamincanac Yes, it works. I update strapi to 4.15.4 & Nuxt to 3.8.2 on Node v18.18.1 |
@BayBreezy just checking. I've upgraded my strapi instance and nuxt to match yours. I'm still having the same issue. On your .env file, under a dev, prod environment that url will need to be what ever the strapi hosting URL is. I'm assuming you have changed that and tested ok? |
Types of changes
Description
When using any node version above 16, the cookie was not being persisted across browser refreshes. Changing "http://localhost:1337" -> "http://127.0.0.1:1337" fixed this issue. Refer to this issue: #229
Resolves: #229
Checklist: