I'm getting 400 Bad Request when pushing an event. But the request is updated in the pusher dashboard.
This is the same issue reported in This Ticket, but it didn't solve my problem so far.
I managed to solve my problem. Basically what I did is update composer again. The version of vender files do a massive part in the Laravel application.
Related
Good afternoon, let me ask
I created a service API using Laravel, but one of the API urls when I sent the response parameter was 403 or Forbidden. even though before it was fine, it worked smoothly. And I raised it to the server instead it became Forbide. Anyone know why? thank you for answering
If it is ok on local and getting a forbidden error on the server, the problem might be caused by the webserver application. please take a look at this link.
I deploy my Laravel + vue project on the Digitalocean apps and some of my api are working but some are not.
When I look into the api response I received message: "Server Error",
But the api is working on localhost and gives error after the deployment.
Is there a way to view the actual error message of the api reponse? so that I can easily understand what causing the error and fix it.
But I really find it weird that it causing error in the digitalocean apps, but works on my local machine.
I've tried searching for hours how to view the errors but I can't find it.
please help me. Thank you!
You can log in to your server and look in the file storage/logs/laravel.log.
Otherwise, I would suggest using a service such as Bugsnag or Sentry, which have integrations with laravel and will give you a dashboard with all your errors
Some people suggest putting APP_DEBUG to true, but that is a security risk as your customers will be able to see the error as well, and you should never do this on a production server
I'm not managing to solve a problem related to the mentioned error in my application.
Looking for a solution I only find information about how to handle CSRF-tokens and can find anything else, is it possible that if I get this error it has to be a problem with the token?
I'm sending a post requests with axios, from a vue component to Laravel.
Edit: I didn't add the code because I know there are already a lot of threads talking about this, I was just wandering if anyone has ever got this error in some case other than CSRF-token related issue.
set in your axios code request
xmlhttp.setRequestHeader("Content-type", "application/x-www-form-urlencoded");
and set cookie
xmlhttp.setRequestHeader('X-CSRF-TOKEN',window.Cookies.get('_csrf'));
If you are using web routes to call as API then you would get this error on POST request. Please define the API routes in api.php and it will start working.
One of my pages in the application triggers a lot of AJAX requests. After a while, I even got a 401 error. How can I solve this problem?
Our API requests have started failing with the error "Request header field yammer-capabilities is not allowed by Access-Control-Allow-Headers".
Before the weekend, everything was working correctly.
Anyone else seeing this?
Same problem here, but it is not the first time, and I think we shouldn't change anything: Yammer's API is slowly beginning to be migrated to Office365's API, maybe this is why there is so much errors in this API... (hope so!)
If you want to see what they're working on :
https://about.yammer.com/success/engage/grow-your-network/release-schedule
Btw, did you try to post this issue on yammer Developer Network ? This can really help, they are using there own social network to communicate ;)