2017-04-04 93 views
1

我有一個laravel版本4.2,它可以在php 5.4,5.5的登錄部分正常工作。但是當我切換到5.6.23時,它開始生成多個會話。我從auth :: attempt獲得成功,但在重定向到儀表板之後,所有事情都沒有了,季節也沒有了。我有檢查會話文件夾會話存在他們,但是,重定向後生成2-3多會話。laravel 4.2重新生成會話重定向

<?php 

返回陣列(

/* 
|-------------------------------------------------------------------------- 
| Default Session Driver 
|-------------------------------------------------------------------------- 
| 
| This option controls the default session "driver" that will be used on 
| requests. By default, we will use the lightweight native driver but 
| you may specify any of the other wonderful drivers provided here. 
| 
| Supported: "file", "cookie", "database", "apc", 
|   "memcached", "redis", "array" 
| 
*/ 

'driver' => 'file', 

/* 
|-------------------------------------------------------------------------- 
| Session Lifetime 
|-------------------------------------------------------------------------- 
| 
| Here you may specify the number of minutes that you wish the session 
| to be allowed to remain idle before it expires. If you want them 
| to immediately expire on the browser closing, set that option. 
| 
*/ 

'lifetime' => 120, 

'expire_on_close' => false, 

/* 
|-------------------------------------------------------------------------- 
| Session File Location 
|-------------------------------------------------------------------------- 
| 
| When using the native session driver, we need a location where session 
| files may be stored. A default has been set for you but a different 
| location may be specified. This is only needed for file sessions. 
| 
*/ 

'files' => storage_path().'/sessions', 

/* 
|-------------------------------------------------------------------------- 
| Session Database Connection 
|-------------------------------------------------------------------------- 
| 
| When using the "database" or "redis" session drivers, you may specify a 
| connection that should be used to manage these sessions. This should 
| correspond to a connection in your database configuration options. 
| 
*/ 

'connection' => null, 

/* 
|-------------------------------------------------------------------------- 
| Session Database Table 
|-------------------------------------------------------------------------- 
| 
| When using the "database" session driver, you may specify the table we 
| should use to manage the sessions. Of course, a sensible default is 
| provided for you; however, you are free to change this as needed. 
|sessions 
*/ 

'table' => 'sessions', 

/* 
|-------------------------------------------------------------------------- 
| Session Sweeping Lottery 
|-------------------------------------------------------------------------- 
| 
| Some session drivers must manually sweep their storage location to get 
| rid of old sessions from storage. Here are the chances that it will 
| happen on a given request. By default, the odds are 2 out of 100. 
| 
*/ 

'lottery' => array(2, 100), 

/* 
|-------------------------------------------------------------------------- 
| Session Cookie Name 
|-------------------------------------------------------------------------- 
| 
| Here you may change the name of the cookie used to identify a session 
| instance by ID. The name specified here will get used every time a 
| new session cookie is created by the framework for every driver. 
|myapp_session 
*/ 

'cookie' => 'myapp_session', 

/* 
|-------------------------------------------------------------------------- 
| Session Cookie Path 
|-------------------------------------------------------------------------- 
| 
| The session cookie path determines the path for which the cookie will 
| be regarded as available. Typically, this will be the root path of 
| your application but you are free to change this when necessary. 
| 
*/ 

'path' => '/', 

/* 
|-------------------------------------------------------------------------- 
| Session Cookie Domain 
|-------------------------------------------------------------------------- 
| 
| Here you may change the domain of the cookie used to identify a session 
| in your application. This will determine which domains the cookie is 
| available to in your application. A sensible default has been set. 
| 
*/ 

'domain' => '', 

/* 
|-------------------------------------------------------------------------- 
| HTTPS Only Cookies 
|-------------------------------------------------------------------------- 
| 
| By setting this option to true, session cookies will only be sent back 
| to the server if the browser has a HTTPS connection. This will keep 
| the cookie from being sent to you if it can not be done securely. 
| 
*/ 

'secure' => false, 

);

我的表單操作處理程序

public function verify() 
{ 
    $username = Input::get('username'); 
    $password = Input::get('password'); 
    if (!User::count()) { 
     $user = new User; 
     $user->username = Input::get('username'); 
     $user->password = $user->password = Hash::make(Input::get('password')); 
     $user->save(); 
     return Redirect::to('/admin/login'); 
    } else { 
     if (Auth::attempt(array('username' => $username, 'password' => $password))) { 

      Session::put('username', $username); 
      if (Session::has('pre_admin_login_url')) { 
       $url = Session::get('pre_admin_login_url'); 
       Session::forget('pre_admin_login_url'); 
       return Redirect::to($url); 
      } else { 

       return Redirect::to('/admin/dashboard')->with('notify','installation Notification'); 
      } 
     } else { 
      return Redirect::to('/admin/login?error=1'); 
     } 
    } 

} 

我試圖改變這一切的價值,已檢查有沒有在PHP中的任意開始標記沒有空間或新行..請幫助我不想升級整個項目版本..謝謝

+0

最後我解決了它在我自己..經過16小時的RND(bocz我是newbee laraval)。我發現,你必須停止在這個函數..protected功能作出新的ID爲sessoion generateSessionId() \t { \t \t //返回SHA1(uniqid( '',真).str_random(25).microtime(真) ); \t \t return md5('sunny_fixed_issue'); \t} path:vendor \ laravel \ framework \ src \ Illuminate \ Session \ Store.php .......至少它解決了我的問題。希望它也能幫助你 –

回答

-1

我有同樣的問題,我解決了它在這些文件結束之前刪除空格和行。