2017-04-04 6 views
1

私はlaravelバージョン4.2を持っており、ログインセクションのphp 5.4,5.5で正常に動作しています。しかし私が5.6.23に切り替えると、genrate multiple sessionが始まりました。私はauth ::試みから成功を収めていますが、ダッシュボードにリダイレクトした直後はすべてがなくなり、シーズンは何もありません。セッションのチェックフォルダがありますが、リダイレクト後に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

最後に、私はそれを私自身で解決しました.RNDの16時間後に(ボラシの私は新生児からララバルへ)。この関数で新しいIDを作成するのを止めなければならないことがわかりました。..protected function generateSessionId() \t { \t \t // return sha1(uniqid( ''、true).str_random(25).microtime(true) ); \t \t return md5( 'sunny_fixed_issue'); \t}パス:vendor \ laravel \ framework \ src \ Illuminate \ Session \ Store.php .......少なくともそれは私の問題を解決しました。それもあなたを助けることを願って –

答えて

-1

私は同じ問題を抱えていましたが、私はこれらのファイルの最後にも空白と行を削除して解決しました。

関連する問題