Description
Laravel Version
12
PHP Version
8.1.31
Database Driver & Version
No response
Description
In the file Illuminate\Foundation\Vite, the method assetPath() is defined as follows:
protected function assetPath($path, $secure = null)
{
return ($this->assetPathResolver ?? asset(...))($path, $secure);
}
However, when the fallback asset(...) function is used, the $secure parameter is not passed in the actual call to assetPath(). For example
$this->assetPath("{$buildDirectory}/{$chunk['file']}")
The $secure argument is omitted in such cases, which causes asset URLs to be generated using HTTP even in HTTPS environments (e.g., in hosting platforms like (Railway).
This behavior may go unnoticed in local development, but it becomes critical in production environments where asset() needs to generate secure URLs (HTTPS), especially when mixed content warnings appear in browsers.
Steps To Reproduce
1 - Create new laravel 12 project with breeze
2 - Deploy the project in railway
3 - Run the application