I've tested usingminifiedAjax method, but columns ordering and search is not working (applied). Data is transmitted, but with model default ordering. I can see lesser GET params are sent which does not cause 404 anymore, but maybe some necessary info is being stripped?

Looks like a step in the right direction 👍

My observations:
-I feel that sending data thru GET with PHP format is too much. If you take APIs, the format is generally very compact such as?q=search-value&f=field1|field2|field3&o=field1,asc|field2,desc. I don't know all the intricacies of DataTables, so I may not be aware of some limitations...
-I think also sticking to GET method is necessary, since POST is for something else

Hey, just noticed that using
->ajax(url('admin/users'))
does not seem to cause 404 errors anymore
..maybe it's a coincidence? same table and config as before

@isometriq thanks for testing. I forgot to commit the changes needed on the main repo. Updates released on v7.8.1. Kindly check again.

Ok, I will try soon
However, in my last test, the->ajax() method this did not cause 404 anymore
Are we supposed to still use it or->minifiedAjax() only?

I suggest to useminifiedAjax because it is indeed a weird bug where Laravel RANDOMLY returns 404 on valid routes. I also encountered that way back and was really confused on what's happening :).

On Laravel 5.5 release, I think I will also default it tominifiedAjax. Can't do it now cause its a potential BC.

This is not a fix for very big table. Still generating very long url even after minifiedAjax applied.
POST method is an only way for some case. But current version of laravel-datatables-button not support for POST method.

@herzcthu Does the issue occurs only export? If yes, then maybe this PRyajra/laravel-datatables-buttons#41 would help?