Sessiyalarni boshqarish. Reja: sessiyalarni boshqarish

2.namespace App\Http\Middleware;

use Closure;

use Illuminate\Session\Middleware\StartSession;

class AppStartSession extends StartSession

{
protected function sessionConfigured(){
if(!\Request::has('api_key')){
return false;
}else{
return parent::sessionConfigured();
}
}
}
kernel.php (o'zgarishlarni amalga oshirish uchun *** izohiga qarang)

namespace App\Http;

use Illuminate\Foundation\Http\Kernel as HttpKernel;

class Kernel extends HttpKernel

{
/**
* The application's global HTTP middleware stack.
*
* @var array
*/
protected $middleware = [
\Illuminate\Foundation\Http\Middleware\CheckForMaintenanceMode::class,
\App\Http\Middleware\EncryptCookies::class,
\Illuminate\Cookie\Middleware\AddQueuedCookiesToResponse::class,

//*** Replace start session class

//\Illuminate\Session\Middleware\StartSession::class,
\App\Http\Middleware\AppStartSession::class,

//*** Also comment these ones that depend on there always being a session.

//\Illuminate\View\Middleware\ShareErrorsFromSession::class,
//\App\Http\Middleware\VerifyCsrfToken::class,
];

/**
* The application's route middleware.

*
* @var array
*/
protected $routeMiddleware = [
'auth' => \App\Http\Middleware\Authenticate::class,
'auth.basic' => \Illuminate\Auth\Middleware\AuthenticateWithBasicAuth::class,
'guest' => \App\Http\Middleware\RedirectIfAuthenticated::class,
];
}
Chegarani jang qilmang, quchoqlang!

2
0
tremby

Savolga javob
1i13/3/2016ubэрталабn2016. 13 март 2016 в 8:07
Batafsil
Laravel 5 da faqat StartSession , ShareErrorsFromSession va VerifyCsrfToken middlewares foydalanmang.

Mening ilovamda web guruhidan ushbu uchta middlewaresni yangi shtatli guruhiga ko'chirdim va keyin ushbu shtatli guruhini qo'shildim sessiya haqida bilish kerak bo'lgan marshrutlar (barcha hollarda, mening ilovada kamida web ga qo'shimcha ravishda). Boshqa yo'nalishlar web yoki api guruhlariga tegishli.

Endi shtatli middleware guruhini ishlatmagan marshrutlarga so'rovlar yuborilganda, sessiya kuki-fayllari qaytarib yuborilmaydi.

2
0
Richard A Quadling

Savolga javob
1i20/1/2015ubэрталабn2015. 20 январ 2015 в 9:52
Batafsil
Men shunga o'xshash xususiyatni bajarishga harakat qilyapman.
Bizning API-1 1 yo'nalish - 1-versiya savatidan tashqari, vatansiz hisoblanadi.
Buning uchun app/config/session.php saytida 'haydovchi ni o'rnatish bilan yakun topdim ...
'driver' => 'v1/cart' === Request::getDecodedPath() ? 'native' : 'array',
Hech bir sehr. Avval filtrdan foydalanishga qaramay, lekin bu etarli darajada erta emas edi.

Bu narsalarni qilishning oddiy usuli bo'lib tuyuladi, lekin men biror narsadan bexabar bo'lsam kerak.

Konnektga o'tishni boshqa ishlab chiquvchilar uchun nima xizmat ko'rsatuvchi provayderga joylashtirilgan bo'lsa, xizmat ko'rsatuvchi provayderlar o'rnatilganligi va ular bilan qanday munosabatda bo'lganligini bilmasdan, nima bo'lishini bilish uchun qulay joy ko'rinadi. disk raskadrovka uchun juda ham qiyin.
Nima bo'lganda ham. Umid qilamanki, bu ba'zi foydalanish.
Quyida ko'rsatilgandek ... DYNAMIK BO'LSA, sizning konfiguratsiyangizni ishlating.
Register the service provider.
Bu esa cheklangan foydalanishga olib keladi. Biz v1/sepetni qo'llab-quvvatlashimiz kerak emas ekan, biz ushbu yo'nalishni qoldirib, so'ngra statik konfiguratsiyaga qaytishimiz kerak.