This likely affects lumen and symfony as well, but I haven't tested either.
On a fresh laravel + clockwork install you can reproduce by visiting the web redirect route with a trailing slash (__clockwork/). You will be redirected to __clockwork/__clockwork/app instead of __clockwork/app. The same happens if you set a custom web path.
I am pretty sure this is down to the fact that your web redirect is relative (no leading slash) with browsers interpreting it as relative to that last slash.
Easy ways to address this:
Including a leading slash in the redirect (return new RedirectResponse('/' . $request->path() . '/app');)
Using the laravel redirect() helper which converts the path to an absolute URL (return redirect($request->path() . '/app');) I don't know what the equivalent is for lumen or symfony.
This likely affects lumen and symfony as well, but I haven't tested either.
On a fresh laravel + clockwork install you can reproduce by visiting the web redirect route with a trailing slash (
__clockwork/
). You will be redirected to__clockwork/__clockwork/app
instead of__clockwork/app
. The same happens if you set a custom web path.I am pretty sure this is down to the fact that your web redirect is relative (no leading slash) with browsers interpreting it as relative to that last slash.
Easy ways to address this:
return new RedirectResponse('/' . $request->path() . '/app');
)redirect()
helper which converts the path to an absolute URL (return redirect($request->path() . '/app');
) I don't know what the equivalent is for lumen or symfony.Thoughts?