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
Since it’s possible to force a route to be served over HTTPS it would be cool to have the same ability for route groups too instead of writing a custom filter for that purpose.
Doesn’t work for me. Solution 2 is ignored and Solution 1 throws an error:
ErrorException: Catchable Fatal Error: Argument 2 passed to Illuminate\Routing\Router::group() must be an instance of Closure, array given, called in /Users/maxhoffmann/Sites/laravel4/vendor/laravel/framework/src/Illuminate/Support/Facades/Facade.php on line 169 and defined in /Users/maxhoffmann/Sites/laravel4/vendor/laravel/framework/src/Illuminate/Routing/Router.php line 588
Sorry, catched all exceptions except for 405 and my default message was thrown. My bad! Anyway would be great if this possibility is mentioned in the documentation. Thanks guys!
Since it’s possible to force a route to be served over HTTPS it would be cool to have the same ability for route groups too instead of writing a custom filter for that purpose.
Proposed syntax:
The text was updated successfully, but these errors were encountered: