Home » Php » laravel 4 persisting data ongoing – jquery ajax submit

laravel 4 persisting data ongoing – jquery ajax submit

Posted by: admin November 29, 2017 Leave a comment


I’m having ongoing problems with laravel 4.1 sessions and getting unexpected behaviour.

Depending on how I call the controllers method the session either works or doesn’t My app makes a call to a POST route – to add items to a cart which is a session. For some reason the session does not get updated.However if I make a call to the same function with a GET request the function works as expected.

My routes.php contains these two routes:

Route::get('testAdd', array('uses' => '[email protected]'));

Route::post('products/addToCart', array('uses' => '[email protected]'));

Both point to the same method

The method is currently this (for testing):

public function addToCart() {

  Session::put("addcarttest", "add to cart");
  return json_encode(Session::get('addcarttest'));


If I call the function with the POST method (with form data) I get the expected result and the contents of the session.

However If I then check for the session (using a profiler) it does not exist. The data did not persist.

If I then call the same method using the GET route, I get the expected result but importantly the session persists.

I thought maybe the POST method deleted sessions however once it exists it stays there – if I use the GET method and the sessin exists if I then try the POST method example again the session remains in place – so the POST method doesnt delete the session.

This is driving me crazy – I’ve lost a lot of hours over this and can’t see why.

Am I missing something over how Laravel handles POST v GET ? Why would two different methods make a difference to underlying functions?

What do I need to do to make the session work correctly with POST?


I’ve now tried database driver for the session and am getting the same behaviour.

I’ve taken my test a stage further- I created a basic form and submitted to the url and the method worked as expected. My current form data is submitted by jquery ajax and assumed they were fairly identical in behviour.

My jquery submit function is this:

     url: '/products/addToCart',
     type: 'POST',
     async: false,
     .done(function() {
     .fail(function() {
     .always(function() {

 return false;

I set async to false – I assume to await the server response. (doesnt work if true either).

So the problem is a subtle difference between a form submit and an ajax submit. Both methods are hitting the same route and method – one saves the session data – the other one doesnt.

How can I overcome? Jquery submit is essential to this part of the app.



I found a similar problem relating to laravel 3. For the session to persist in an ajax call I need to return the response correctly.

return json_encode($response);

This is causing the problem. It’s not it appears a valid response to enable the session to persist. I changed it to:

return Response::json($response); 

This enabled the session to persist!

For some reason a normal form submit or call to the method allows the first one but ajax does not.

I’ve seen references elsewhere about echo statements in the method affecting the session data but did not think I had any – the return I suppose must behaving similar to an echo

Happy now (till the next problem)

This is the post that triggered the solution:


i have same issues, but when returning XML Response, not JSON.

I fixed it using session save.

\Session::put('LOGADO.ID_LOJA', $id_loja.time());


This fixed everything inside AJAX Calls.


This is in reference to the solution that Ray gave.
I had a very similar problem, which your solution resolved. Initially, I had the following on my Controller:

echo json_encode(array('auth' => $auth));

I changed this to:

return Response::json(array('auth' => $auth));

However, this was only part of the solution. In my javascript file, I initially had:

data = $.parseJSON(data);

Which, if I had kept the echo in the controller…would have been needed. apparently Laravel will do some magic behind the scenes when using Response::json() so that the data that is returned is already parsed. Removing that line in my javascript file made everything happy again 🙂