Redirect Intended

So let's say you visit the url http://example.com/admin/post/create but you need to be logged in to visit this page (The route has a middleware of auth). The middleware kicks in and redirects you to the login page. Now when you login you will be redirected to the intented page and that is /admin/post/create.

@bobbybouwmann thank you for your answer but this is not what I meant.

I have a route /foo/{id} and a show method. Depending of the resource found a visitor will need to be authenticated to see the requested resource.

if (  !$foo->is_free && !app('auth')->check()) {
            return redirect('login');
}

So, if he is not authenticated he will be redirected to the login route (which is an alias of the original auth/login). Once the user is logged in I would like hime to be redirected to the requested resource with the intended functionality. For now with my code he is instead redirected to /home.

I found.

I needed to perform the following

return redirect()->guest('auth/login');
//or with my custom route:
return redirect()->guest('login');

Now the intended is working properly.

i use routes with middleware (http://laravel.com/docs/5.0/routing): Route::group(['middleware' => 'foo'], function() { Route::get('/', function() { }); } and here is a sample for custom Auth http://laravel.io/forum/11-04-2014-laravel-5-how-do-i-create-a-custom-auth-in-laravel-5

Yeah you kinda have it backwards, intended uses the referrer in which you came from. You shouldn't need to use ->guest()

@bashy thank you. Without ->guest() it is not working. Inside trait AuthenticatesAndRegistersUsers and the method postLogin() I tried dd(Session::has('url.intended')) and it returns false.

Probably because of a double redirect, have you checked with cURL?

curl -IL http(s)://example.com/some/resource/1

@bashy I just did.

I'm logged out. I hit the some/resource/1 and it redirects me to the login route. I complete the form (Laravel defaults), submit and I'm redirected to the /home route.

If I had the ->guest('login') I'm instead redirected to the intended some/resource/1 route.

The output of the curl command is the following:

HTTP/1.1 302 Found
Server: nginx/1.6.2
Content-Type: text/html; charset=UTF-8
Connection: keep-alive
Cache-Control: no-cache
Date: Sun, 24 May 2015 15:33:27 GMT
Location: http://xxx.app/login
...

HTTP/1.1 200 OK
Server: nginx/1.6.2
Content-Type: text/html; charset=UTF-8
Connection: keep-alive
Cache-Control: no-cache
Date: Sun, 24 May 2015 15:33:27 GMT
...