Viewed   867 times

This is my test ajax in laravel 5 (refer below)

    var url = $(this).attr("data-link");
        url: "test",
        data: { testdata : 'testdatacontent' },
    }); //end of ajax

and the trigger link

<a href="#" id="try" data-link="{{ url('/test') }}">Try</a>

and my route

Route::post('test', function()
    return 'Success! ajax in laravel 5';

but it gives me an error when I run the console in google chrome and it doesn't return the expected response "return 'Success! ajax in laravel 5';"

POST 500 (Internal Server Error)

whats wrong/problem to my code? anything I'm missing?



While this question exists for a while, but no accepted answer is given I'd like to point you towards the solution. Because you're sending with ajax, and presumably still use the CSRF middleware, you need to provide an additional header with your request.

Add a meta-tag to each page (or master layout): <meta name="csrf-token" content="{{ csrf_token() }}">

And add to your javascript-file (or section within the page):

  headers: {
    'X-CSRF-TOKEN': $('meta[name="csrf-token"]').attr('content')

See for more details.

Sunday, October 30, 2022

You're accessing the ajax() method statically (using ::), when you should be using -> instead:

if ($request->ajax()) {

Using the Laravel log file

As mentioned in the comments, Laravel is probably telling you this in storage/logs/laravel.log, complete with a long call-stack trace (the lines that you mentioned, beginning with "#38" and "#39"). Just scroll up to before "#1" and you'll find your culprit.

Wednesday, December 21, 2022

you actually must use ajax technology for this .. but only once .. let the angularJS or vue do the searching function .. i actually wanted to post a snippet here but there's seems to be a bug .. so here's a sample you might wanna see ..

Thursday, October 20, 2022

Your $.ajaxPrefilter approach is a good one. You don't need to add a header, though; you simply need to add a property to the data string.

Data is provided as the the second argument to $.post, and then formatted as a query string (id=foo&bar=baz&...) before the prefilter gets access to the data option. Thus, you need to add your own field to the query string:

var csrf_token = $('meta[name="csrf-token"]').attr('content');
$.ajaxPrefilter(function(options, originalOptions, jqXHR){
    if (options.type.toLowerCase() === "post") {
        // initialize `data` to empty string if it does not exist = || "";

        // add leading ampersand if `data` is non-empty +="&":"";

        // add _token entry += "_token=" + encodeURIComponent(csrf_token);

This will turn id=userID into id=userID&_token=csrf_token.

Wednesday, December 7, 2022

The first stop here would be to enable Failed Request Tracing:

Troubleshooting Failed Requests Using Tracing in IIS 7
Troubleshoot with Failed Request Tracing

If doesn't produce anything that narrows things down then have a trawl through the System and Application Event logs.

Finally if it's still not obvious what's failing then it's time to dig out some toys from Tess Ferrandez's debugging toolbox:

.NET Debugging Demos - Information and setup instructions

.NET Debugging Demos Lab 2: Crash

.NET Debugging Demos Lab 5: Crash

.NET Debugging - Crash Scenarios

Friday, September 16, 2022
Only authorized users can answer the search term. Please sign in first, or register a free account.
Not the answer you're looking for? Browse other questions tagged :