Qfyilyi

I have the following route in my routes/web.php file of Laravel 5.7.

Route::match(['get', 'post', 'put', 'delete'], '{request}', function ($request) {

    return redirect('api/'.$request);

})->where('request', '^(?!api).*');

This route rule checks for any routes that does not start with "api", prepend "api" to the route and redirect it.

This works well for GET requests but does not work for POST, PUT or DELETE requests. I get an HttpException when I attempt to POST something. If I define individual POST, PUT or DELETE route in the routes/web.php file, I get the same result. The request seems to fail immediately hence the route is never executed or fails during execution.

Route::post('some/feature/{feature_id}/{sub_feature_id}', 'API/SomeFeature@store');

Here is the exception I get.

{

    "exception": "Symfony\Component\HttpKernel\Exception\HttpException",

    /* ... */

}

We have an old system that uses the following routing structure.
feature/{feature_id}/{sub_feature_id}

The new system I am working on has the following routing structure.
api/v1/feature/{feature_id}/sub_feature/{sub_feature_id}

What I need to do is redirect all requests not starting with api to their counterparts in the new system.

If I define the routes of the old system in the routes/api.php routes file, they automatically get prefixed with "api" which is not my desired behaviour because our old system does not have "api" prefixed.

Are there any way I can get this to work for POST, PUT and DELETE requests?

My best guess is those verbs are disabled in routes/web.php for API based requests and only executes when submitted by a form on the same domain. Alternatively it may be CSRF blocking the request, perhaps something that I am missing.

Any advise would be highly appreciated.