Resources can't be loaded if laravel path contains a prefix #140
Comments
|
It seems this small code within the HealthController's panel method is enough, but i don't know if there are other places to look for: $config = config('health');
foreach($config['routes']['list'] as $i => $route) {
$config['routes']['list'][$i]['uri'] = url($route['uri']);
}
return response((string) view(config('health.views.panel'))->with('laravel', ['health' => $config])); |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Issue #115 described problems when laravel had been installed to a subfolder. This has been fixed in 0.9.16. But there's still another problem with subfolders if you are using a path prefix which seems not to be fixed the change.
Background: Laravel path prefix
Take for example you have a laravel application at
http://example.com/monitoringapp. If you use a webserver like caddy you can point the domain's path prefixmonitoringappto a laravel installation in a specific folder (e.g./var/www/laravel-monitoring). Everything works correct when you include the path prefix in your.env(APP_URL=http://example.com/monitoringapp):/health/checkbecause the/monitoringappprefix must not be used when registering routes! (laravel will "ignore" the/monitoringappwhen routing)Problem
The code is using the
routes.list[*].uriroute path directly for axios to load the information. But this will point to/health/*and not/monitoringapp/health/*. Theroutes.prefixvalue can not be changed as described because the route has to be registered without the/monitoringappprefix. So the javascript code can not load the information.Solution
Use laravel's url helper to generate absolute urls for axios, because it does now how to create the correct one:
config('health.routes.list[0].uri')=>/health/panelWRONGroute(config('health.routes.list[0].name'))=>http://example.com/monitoringapp/health/panelCORRECTUsing the url-helper to generate the url for axios may probably solve many more problems with "esoteric" configurations how urls are mapped within laravel because it's relying on the same logic every url is routed within laravel.
The text was updated successfully, but these errors were encountered: