You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for reporting. Managed to reproduce this one but the way I see it is that this is intended from how things work. The framework is never booted when a custom template is set so the exclude array cannot be reached.
I do think it's possible to solve this by adding the exclude list to the down file so it can be checked in the maintenance.php file.
Description:
While being in maintenance mode having a custom template, the excluded URIs are not served.
It works fine in case of template = null
Steps To Reproduce:
App\Http\Middleware\PreventRequestsDuringMaintenance
$except
propertyartisan down --render={any template}
and visit the excluded URlsIn opposite case, if you write on cli
artisan down
(without render option) and visit the excluded URls, they will be servedInfo: the issue seems to be on:
framework/src/Illuminate/Foundation/Console/stubs/maintenance-mode.stub
Line 12 in 83b7054
The text was updated successfully, but these errors were encountered: