<?php12use Illuminate\Support\Str;34return [5/*6|--------------------------------------------------------------------------7| Default Session Driver8|--------------------------------------------------------------------------9|10| This option determines the default session driver that is utilized for11| incoming requests. Laravel supports a variety of storage options to12| persist session data. Database storage is a great default choice.13|14| Supported: "file", "cookie", "database", "apc",15| "memcached", "redis", "dynamodb", "array"16|17*/1819'driver' => env('SESSION_DRIVER', 'redis'),2021/*22|--------------------------------------------------------------------------23| Session Lifetime24|--------------------------------------------------------------------------25|26| Here you may specify the number of minutes that you wish the session27| to be allowed to remain idle before it expires. If you want them28| to expire immediately when the browser is closed then you may29| indicate that via the expire_on_close configuration option.30|31*/3233'lifetime' => env('SESSION_LIFETIME', 720),3435'expire_on_close' => env('SESSION_EXPIRE_ON_CLOSE', false),3637/*38|--------------------------------------------------------------------------39| Session Encryption40|--------------------------------------------------------------------------41|42| This option allows you to easily specify that all of your session data43| should be encrypted before it's stored. All encryption is performed44| automatically by Laravel and you may use the session like normal.45|46*/4748'encrypt' => env('SESSION_ENCRYPT', true),4950/*51|--------------------------------------------------------------------------52| Session File Location53|--------------------------------------------------------------------------54|55| When utilizing the "file" session driver, the session files are placed56| on disk. The default storage location is defined here; however, you57| are free to provide another location where they should be stored.58|59*/6061'files' => storage_path('framework/sessions'),6263/*64|--------------------------------------------------------------------------65| Session Database Connection66|--------------------------------------------------------------------------67|68| When using the "database" or "redis" session drivers, you may specify a69| connection that should be used to manage these sessions. This should70| correspond to a connection in your database configuration options.71|72*/7374'connection' => env('SESSION_CONNECTION'),7576/*77|--------------------------------------------------------------------------78| Session Database Table79|--------------------------------------------------------------------------80|81| When using the "database" session driver, you may specify the table to82| be used to store sessions. Of course, a sensible default is defined83| for you; however, you're welcome to change this to another table.84|85*/8687'table' => env('SESSION_TABLE', 'sessions'),8889/*90|--------------------------------------------------------------------------91| Session Cache Store92|--------------------------------------------------------------------------93|94| When using one of the framework's cache driven session backends, you may95| define the cache store which should be used to store the session data96| between requests. This must match one of your defined cache stores.97|98| Affects: "apc", "dynamodb", "memcached", "redis"99|100*/101102'store' => env('SESSION_STORE'),103104/*105|--------------------------------------------------------------------------106| Session Sweeping Lottery107|--------------------------------------------------------------------------108|109| Some session drivers must manually sweep their storage location to get110| rid of old sessions from storage. Here are the chances that it will111| happen on a given request. By default, the odds are 2 out of 100.112|113*/114115'lottery' => [2, 100],116117/*118|--------------------------------------------------------------------------119| Session Cookie Name120|--------------------------------------------------------------------------121|122| Here you may change the name of the session cookie that is created by123| the framework. Typically, you should not need to change this value124| since doing so does not grant a meaningful security improvement.125|126*/127128'cookie' => env(129'SESSION_COOKIE',130Str::slug(env('APP_NAME', 'pterodactyl'), '_') . '_session'131),132133/*134|--------------------------------------------------------------------------135| Session Cookie Path136|--------------------------------------------------------------------------137|138| The session cookie path determines the path for which the cookie will139| be regarded as available. Typically, this will be the root path of140| your application, but you're free to change this when necessary.141|142*/143144'path' => env('SESSION_PATH', '/'),145146/*147|--------------------------------------------------------------------------148| Session Cookie Domain149|--------------------------------------------------------------------------150|151| This value determines the domain and subdomains the session cookie is152| available to. By default, the cookie will be available to the root153| domain and all subdomains. Typically, this shouldn't be changed.154|155*/156157'domain' => env('SESSION_DOMAIN'),158159/*160|--------------------------------------------------------------------------161| HTTPS Only Cookies162|--------------------------------------------------------------------------163|164| By setting this option to true, session cookies will only be sent back165| to the server if the browser has a HTTPS connection. This will keep166| the cookie from being sent to you when it can't be done securely.167|168*/169170'secure' => env('SESSION_SECURE_COOKIE'),171172/*173|--------------------------------------------------------------------------174| HTTP Access Only175|--------------------------------------------------------------------------176|177| Setting this value to true will prevent JavaScript from accessing the178| value of the cookie and the cookie will only be accessible through179| the HTTP protocol. It's unlikely you should disable this option.180|181*/182183'http_only' => env('SESSION_HTTP_ONLY', true),184185/*186|--------------------------------------------------------------------------187| Same-Site Cookies188|--------------------------------------------------------------------------189|190| This option determines how your cookies behave when cross-site requests191| take place, and can be used to mitigate CSRF attacks. By default, we192| will set this value to "lax" to permit secure cross-site requests.193|194| See: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie#samesitesamesite-value195|196| Supported: "lax", "strict", "none", null197|198*/199200'same_site' => env('SESSION_SAME_SITE', 'lax'),201202/*203|--------------------------------------------------------------------------204| Partitioned Cookies205|--------------------------------------------------------------------------206|207| Setting this value to true will tie the cookie to the top-level site for208| a cross-site context. Partitioned cookies are accepted by the browser209| when flagged "secure" and the Same-Site attribute is set to "none".210|211*/212213'partitioned' => env('SESSION_PARTITIONED_COOKIE', false),214];215216217