PHP Fatal error: Uncaught Error: Class "Laravel\Octane\Octane" not found in /Users/alberto/Projects/ThinkOutside/rejux-back/vendor/laravel/octane/src/Stream.php:56
Stacktrace:
#0 /Users/alberto/Projects/ThinkOutside/rejux-back/vendor/laravel/octane/bin/createSwooleServer.php(19): Laravel\Octane\Stream::shutdown(Object(Swoole\Exception))
#1 /Users/alberto/Projects/ThinkOutside/rejux-back/vendor/laravel/octane/bin/swoole-server(35): require('/Users/alberto/...')
#2 {main}
thrown in /Users/alberto/Projects/ThinkOutside/rejux-back/vendor/laravel/octane/src/Stream.php on line 56
Fatal error: Uncaught Error: Class "Laravel\Octane\Octane" not found in /Users/alberto/Projects/ThinkOutside/rejux-back/vendor/laravel/octane/src/Stream.php:56
This is after updating the Octane version 2.3.2 to the latest 2.3.4, in order to solve other problems that are worth a new issue, but I will also give a brief explanation:
I noticed that in lower versions of octane there was security using JWT token, but in version 2.3.2 I am facing a problem with a security flaw.
When generating the token, I do not need to send it in the authorization Bearer header....
Even though the routes are in the auth:api middleware, they return data without passing the Bearer token.
Testing in other applications with older versions of octane, we do not have this problem.
I updated an older application to the latest version of octane and it did not show the error. I will close my issue until I can better identify what happened.
Octane Version
2.3.4
Laravel Version
10.46.0
PHP Version
8.2.11
What server type are you using?
Swoole
Server Version
5.0.3
Database Driver & Version
Postgres 14
Description
I get the following error:
This is after updating the Octane version
2.3.2
to the latest2.3.4
, in order to solve other problems that are worth a new issue, but I will also give a brief explanation:I noticed that in lower versions of octane there was security using JWT token, but in version 2.3.2 I am facing a problem with a security flaw.
When generating the token, I do not need to send it in the authorization Bearer header....
Even though the routes are in the auth:api middleware, they return data without passing the Bearer token.
Testing in other applications with older versions of octane, we do not have this problem.
Steps To Reproduce
When starting the server with the command: