狂饮返回500错误

Question

So im new to guzzle and building API's , I have used Laravel Passport and on one GET call its fine. 因此，对于刚开始构建API而言，我是新手，我使用过Laravel Passport，并且在一个GET调用中就很好了。 I have written a POST call and getting a 500 error in return 我写了一个POST呼叫，但返回500错误

Post function 发布功能

  public function newsSingle() {
            $request = (new GuzzleHttp\Client)->post('http://138.68.180.100/news/article/single', [
                'headers' => [
                    'Authorization' => 'Bearer '.session()->get('token.access_token'),
                    'post_id' => $_POST['post_id']
                ]
            ]);
            $news = json_decode((string)$request->getBody());
            return view('pages.newsingle', compact('news'));
}

Which does add the post item POST Data post_id "3" 哪个确实添加了发布项目POST数据post_id“ 3”

on the other end I have 另一方面，我有

Route: 路线：

Route::post('news/article/single', 'ApiController@singlePost')->middleware('auth:api');

Controller function: 控制器功能：

public function singlePost(Request $request) {
        $article = Articles::where('id', $request['post_id'])->get();
        return $article;
    }

my error: 我的错误：

Server error: `POST http://ipaddress/news/article/single` resulted in a `500 Internal Server Error` response: <!DOCTYPE html> <html> <head> <meta charset="UTF-8" /> <meta name="robots" content="noindex,nofollow (truncated...)

Answer 1

We found the similar issue with Guzzle for External API calls when response code is 500 and got Server error: and exception is thrown. 当响应代码为500并出现Server error:时，我们发现Guzzle进行了外部API调用的类似问题Server error:并引发了异常。 There is a work around to do a bypass mechanism by catching the exception due to BadResponseException to return as response. 可以通过捕获BadResponseException导致的异常以作为响应返回来绕过机制。 below is the code for performing this. 下面是执行此操作的代码。 :) :)

catch (\GuzzleHttp\Exception\BadResponseException $e) {
    return $e->getResponse()->getBody()->getContents();
}

狂饮返回500错误

问题描述

1 个解决方案

解决方案1
0 2019-07-09 13:04:00

狂饮返回500错误

问题描述

1 个解决方案

解决方案1 0 2019-07-09 13:04:00

解决方案1
0 2019-07-09 13:04:00