Level 102
You cannot use env() outside of config files in production. So this $key = env('API_KEY'); needs to be moved to a config file.
I suggest you read the [!] part here: https://laravel.com/docs/9.x/configuration#configuration-caching
Jun 30, 2022
8
Level 6
Getting a 400 when requesting API on remote server but 200 when requesting locally
Hi all
I'm seeing some strange behaviour on my remote server that I'm not sure how to debug. I execute the following code to make an API request:
$my_field_value= '123';
$key = env('API_KEY');
$username = env('API_USERNAME');
$model = MyModel::where('my_field', $my_field_value)->first();
$meta_url = 'https://[url_to_api].com/path/thats/relevant/api?username=' . $username
.'&key=' . $key;
$meta_response = Http::get($meta_url);
dd($meta_response);
When I execute this code locally, I get a 200, but if I execute exactly the same code on my remote server I get a 400. What could be causing this issue, and how can I go about debugging it?
Level 6
@Sinnbeck Thanks Sinbeck. I'll change that now. Strange thing is when I print the $meta_url, I still got the environmental variable included?
Level 102
@verster.cornel@gmail.com In production or locally?
Level 6
@Sinnbeck In production. Thanks for the tip, I've moved everything to a config file that references .env, but unfortunately I'm still getting the same 400 error (though if I check the http response, the url is correct and I can execute it in my browser with the desired response, a 200).
Level 102
@verster.cornel@gmail.com Is there any way you can ask the people who has the api why they see the request as malformed then? I assume you can copy paste it into a browser and it will just work there?
Level 6
@Sinnbeck Yeah I'll do that, thanks! I just wanted to make sure I'm not doing something obvious wrong that would be different between my local and prod environments. Could running composer update on prod (which I did to get rid of a Log depreciation error) maybe have caused a change in how my Http client operates?
Level 102
@verster.cornel@gmail.com That is why you have a composer.lock file. When you deploy, you run composer install, to install exactly the same versions as in development. That way you dont get any surprices.
But the code looks fine, except for those 2 env calls :)
1 like
Level 122
try to curl that url from the server command line
Please or to participate in this conversation.