I have a
laravel app which is my main website and now have an API built with
So far the setup is like so
client(user) ----> webserver(laravel) -----> API server(lumen)
Now traditionally, all
session related duties will be carried out by the
webserver things like logging in a user.
webserver runs a script that checks
db for user and then if valid starts a
session and then sends a
session cookie back to the user to identify them later.
Now I presume that what happens if I move those scripts to the
API server is that a client requesting to
login will tell that to the
webserver who will then go off to the
API server. The
API server performs the
db check and if valid starts a
session and sends a
session cookie back to the
webserver and thats it because to the
API server the
webserver is the client so the user never get’s a
session cookie saved in his browser rather the
session is between the
Please can anyone confirm if this is correct. As I’ve deployed this exact infrastructure and this is the behaviour I’m observing.
Is this setup even advisable or possible?
How can i implement something similar to this where the
API server does all the work and the
webserver simply holds the
from Newest questions tagged laravel-5 – Stack Overflow http://ift.tt/1PJwFVz