Windows NT WIN-F6SLGVICLOP 10.0 build 17763 (Windows Server 2016) AMD64
Microsoft-IIS/10.0
Server IP : & Your IP : 3.22.249.82
Domains :
Cant Read [ /etc/named.conf ]
User : elibrary.unsap.ac.id
Terminal
Auto Root
Create File
Create Folder
Localroot Suggester
Backdoor Destroyer
Lock Shell
Lock File++
Readme
D: /
localhost /
trash /
config /
Delete
Unzip
Name
Size
Permission
Date
Action
app.php
6.3
KB
-rw-rw-rw-
2024-01-16 21:55
auth.php
4.2
KB
-rw-rw-rw-
2024-01-16 21:55
broadcasting.php
2.1
KB
-rw-rw-rw-
2024-01-16 21:55
cache.php
3.26
KB
-rw-rw-rw-
2024-01-16 21:55
cors.php
846
B
-rw-rw-rw-
2024-01-16 21:55
database.php
5.17
KB
-rw-rw-rw-
2024-01-16 21:55
filesystems.php
2.31
KB
-rw-rw-rw-
2024-01-16 21:55
hashing.php
1.59
KB
-rw-rw-rw-
2024-01-16 21:55
logging.php
4.08
KB
-rw-rw-rw-
2024-01-16 21:55
mail.php
3.95
KB
-rw-rw-rw-
2024-01-16 21:55
queue.php
3.37
KB
-rw-rw-rw-
2024-01-16 21:55
sanctum.php
2.9
KB
-rw-rw-rw-
2024-01-16 21:55
services.php
979
B
-rw-rw-rw-
2024-01-16 21:55
session.php
7.32
KB
-rw-rw-rw-
2024-01-16 21:55
view.php
1.03
KB
-rw-rw-rw-
2024-01-16 21:55
Save
Rename
<?php use Laravel\Sanctum\Sanctum; return [ /* |-------------------------------------------------------------------------- | Stateful Domains |-------------------------------------------------------------------------- | | Requests from the following domains / hosts will receive stateful API | authentication cookies. Typically, these should include your local | and production domains which access your API via a frontend SPA. | */ 'stateful' => explode(',', env('SANCTUM_STATEFUL_DOMAINS', sprintf( '%s%s', 'localhost,localhost:3000,127.0.0.1,127.0.0.1:8000,::1', Sanctum::currentApplicationUrlWithPort() ))), /* |-------------------------------------------------------------------------- | Sanctum Guards |-------------------------------------------------------------------------- | | This array contains the authentication guards that will be checked when | Sanctum is trying to authenticate a request. If none of these guards | are able to authenticate the request, Sanctum will use the bearer | token that's present on an incoming request for authentication. | */ 'guard' => ['user', 'admin'], /* |-------------------------------------------------------------------------- | Expiration Minutes |-------------------------------------------------------------------------- | | This value controls the number of minutes until an issued token will be | considered expired. This will override any values set in the token's | "expires_at" attribute, but first-party sessions are not affected. | */ 'expiration' => null, /* |-------------------------------------------------------------------------- | Token Prefix |-------------------------------------------------------------------------- | | Sanctum can prefix new tokens in order to take advantage of numerous | security scanning initiatives maintained by open source platforms | that notify developers if they commit tokens into repositories. | | See: https://docs.github.com/en/code-security/secret-scanning/about-secret-scanning | */ 'token_prefix' => env('SANCTUM_TOKEN_PREFIX', ''), /* |-------------------------------------------------------------------------- | Sanctum Middleware |-------------------------------------------------------------------------- | | When authenticating your first-party SPA with Sanctum you may need to | customize some of the middleware Sanctum uses while processing the | request. You may change the middleware listed below as required. | */ 'middleware' => [ 'authenticate_session' => Laravel\Sanctum\Http\Middleware\AuthenticateSession::class, 'encrypt_cookies' => App\Http\Middleware\EncryptCookies::class, 'verify_csrf_token' => App\Http\Middleware\VerifyCsrfToken::class, ], ];