405 (Method Not Allowed) when validation fails

@Sinnbeck it is vue / Laravel project.

Here is vue component method, the [this.methode] can be post or patch:

onSubmit() {
	this.form[this.methode]('/mobile/pwa-irrigations')
		.then(response => {
			console.log(response)
		})
},

I am using resource route

Route::resource('mobile/pwa-irrigations', 'PwaIrrigationController');

In controller if I return the return $request->all() it works, as soon as it hits validation and validation fails, I get the error message back in response.

public function update(Request $request, Irrigation $pwaIrrigation)
{
	//return $request->all();
	$request->validate(['attr_do_not_exist'=>'required']);
}

Here is the error message I get back in response:

{message: "The PATCH method is not supported for this route. Supported methods: GET, HEAD.",…}
exception: "Symfony\Component\HttpKernel\Exception\MethodNotAllowedHttpException"
file: "E:\wamp64\www\agnote_app\vendor\laravel\framework\src\Illuminate\Routing\AbstractRouteCollection.php"
line: 117
message: "The PATCH method is not supported for this route. Supported methods: GET, HEAD."

And here is the console message:

mobile.js:4444 PATCH http://127.0.0.1:8000/mobile/pwa-irrigations/1197 405 (Method Not Allowed)

If validation passes it works as it is supposed to.

What really puzzles me is that it worked when I initially built it. I have done a lot of other additions/fixes/changes in other places in applications, but nothing in this irrigation functionality, plus this is pretty straight forward, the request does hit the controller, and everything works if validation passes, hmm...

I think somewhere in the Laravel validation on fail is logic like this, but for some reason in validation it is not seeing the request as ajax.

if ($request->ajax())) {
	return new JsonResponse($errors, 422);
}

The validation on fail is not working for both post and patch methods inside controller.

Tricky... :)

@GuntarV yeah my thought as well.

This method seems that it doesn't add the correct headers

this.form

I don't use vue so I don't know if that is a built on thing or your own implemention. Might be helpful if you show the code if it's your own

@Sinnbeck It is my own implementation which I built following one of the Vue 2 tutorials here on Laracasts.

Behind the scenes it is using axios. Once the request hits the controller method, the request does come-in as ajax.

I'll keep figuring out, I do need to get it working :)

@Snapey

do you ask for a json response in your form posting?

How do I do that? I did try this in the axios:

axios[requestType](url, data, params, {headers: {'Content-Type': 'application/json'}})

but that did not change anything, I am still getting back the The PATCH method is not supported for this route. Supported methods: GET, HEAD.

In the controller I checked what's coming in $request->ajax() and $request->wantsJson(), both are true

public function update(Request $request, Irrigation $pwaIrrigation)
{
	//return $request->all();
	dd($request->ajax(),$request->wantsJson());
	$request->validate(['attr_do_not_exist'=>'required']);
	dd('after validation');

If the validation fails, it is redirecting instead of returning 422 json error.

If the validation passes everything works as it should.

@snapey can you please guide me where I can find the logic on what's happening inside validate method? If I ctrl+click on it takes me to Request class,

/**
 * @method array validate(array $rules, ...$params)
 * @method array validateWithBag(string $errorBag, array $rules, ...$params)
 * @method bool hasValidSignature(bool $absolute = true)
 */
class Request extends SymfonyRequest implements Arrayable, ArrayAccess

but I don't know how to get to what's happening inside validate.

Somewhere, when the validation fails, it is redirecting instead of returning error json.

Initially when I built and tested the validation error was returned as 422 json, but at some point, it stopped doing that.

Now I am stuck in the snow :)

@Snapey

It is redirecting to (here is a screenshot): https://prnt.sc/25fp3vo

In the applicaiton I have multiple route groups, here is a short version of two of them:

Route::prefix('mobile')->namespace('Mobile')
    ->middleware(['verified', 'auth', 'account_active'])->group(function () {
        Route::resource('pwa-irrigations', 'PwaIrrigationController');
    });
	
Route::prefix('account')->namespace('Account')
    ->middleware(['verified', 'auth', 'account_active', 'main-app-access'])->group(function () {
        Route::get('map', 'Shared\MapController@index')->name('map');
        Route::get('map/center', 'Shared\MapController@center')->name('account-center');
        Route::get('map/properties/{companyId?}', 'Shared\MapController@properties')->name('account-properties');
        Route::get('map/status-properties/{status}', 'Shared\MapController@statusProperties');
    });	

After doing some random testing, the mobile is where the validation is not working.

From the form, if I send the request to one of the account controllers and force validation to fail, validation returns 422 json as it should.

@Snapey Here are few more images:

• Mobile Headers https://prnt.sc/25fsblz
• Mobile Preview https://prnt.sc/25fsf7t