I noticed that during the development of my Laravel app the return redirect() sometimes doesnt work when I try to register or login into my app. I hit the submit button and the page just keeps loading and I can see that chrome says "processing" and keeps spinning, so I have to manually click the browser refresh button in order to get redirected to the account page meaning that the user successfully logged in or registered.
But sometimes it works just fine which is strange.
So today I tried to clear the Laravel cache and browser cache
php artisan cache:clear
php artisan route:clear
php artisan config:clear
php artisan view:clear
And do a "empty cache and hard reload" on chrome
After that I tried to register a user, and this time redirect didnt work again.
So I checked telescope to look at the headers and noticed this:
The times redirect doesnt work I can see:
referer: "https://www.mysite.test/login",
origin: "https://www.mysite.test",
host: "www.mysite.test"
And the times when redirect works the headers looks like this:
referer: "https://mysite.test/login",
origin: "https://mysite.test",
host: "mysite.test"
So why is "www" added to the url when I clear the cache and why does adding "www" keeps redirect() from working?
I am running my app through Valet if that matters
I don't think this has anything to do with the caching part. The reason it probably worked before is because the working solution was cached. You probably have something wrong in your local setup with Valet or something goes wrong inside your application.
Right now, I don't have enough context for a solution!
I had this problem when I was using
php artisan serve
You would need to stop this, and start it again. In other words sometimes you need to restart your web service to make sure your updated config is used.
noticed you mentioned you are using valet, here is what you can do:
valet restart
then try your redirect again
Also have you tried incognito mode in your browser?
@bobbybouwmann @laracasts_com I will try to restart valet. I am almost sure its not working coz of valet/nginx. I just noticed if I login into "https://mysite.com" then visit "https://www.mysite.com" I am not logged in under that domain since the cookie doesnt seem to be set for both "www" and without "www"
@bugsysha yea same result
Search your project for redirects or changes on APP_URL or config values. Also make sure that this is not happening cause of some composer package that you've included. In the end you can always rm -fr vendor and composer install to see if it helps. Restarting your computer is also an option.
I would definitely suggest using tinker to properly debug this and see where are you getting redirected to www version. If you have not used tinker before watch this: https://laracasts.com/series/laravel-from-scratch-2018/episodes/28
Ok it seemed the problem was that I had to change domain => '.example.com' in my settings, sometimes the app redirected me between www and without www. And the session was not set over the entire domain
So is that happening on production or on local?
@bugsysha I could only see it on my local machine
Strange.
Please or to participate in this conversation.