Ошибка 400 postman - TopOshibok.ru - решение и исправление самых разных ошибок

I’m trying to access an API using Postman to get a response using basic authentication, but when I submit the data, it gives me the dreaded 400 error, which apparently indicates that some headers aren’t set up properly.

Here’s the API info:

Request

Endpoint: {loginUrl}
Data to submit: an email and a password
POST /login HTTP/1.1
Host: {baseUrl}
Accept: application/json
Content-Type: application/json
Content-Length: 68

{
    "email": "{email}",
    "password": "{password}"
}

And in response, I should get an encrypted token in form of JSON, instead I’m getting this error.

Here are the postman screenshots:

Am I missing something?

asked Jan 28, 2018 at 17:28

I also faced the same issue and i updated my postman header with the below image. And issue solved.

answered Aug 11, 2021 at 5:54

From the lack of details it’s difficult to offer a specific answer but I can offer something that you can try — The Request data you posted in the question looks like you should be adding:

{
    "email": "{email}",
    "password": "{password}"
}

In the Body section of the request but your images don’t show that you’ve added that to the Body on any request, you’ve added it as a Auth header instead, so remove that before trying again. I’m not sure of the need to add the Content-Length header as that will change for different username and password combinations in the payload or for the length of the response.

answered Jan 28, 2018 at 19:08

Danny DaintonDanny Dainton

23.2k6 gold badges67 silver badges80 bronze badges

In case anyone finds this helpful, I ran into the same issue and the culprit turned out to be missing headers. I knew I needed the "Content-Type": "application/json" header, which I already had in place, but I didn’t know that I was missing two other headers.

The solution for me was also adding the "Content-Length" and "Host" headers in Postman.

I see some others have questioned the need for the "Content-Length" header, but in my case, the minimum three needed were "Content-Type", "Content-Length", and "Host" or it would always fail.

answered Feb 25, 2022 at 20:03

cf512cf512

714 bronze badges

I faced a similar issue. it got resolved when i called my placeholder as a tuple.

answered Oct 5, 2022 at 10:02

I had the same problem,and I discovered was sending a json body from postman while a text option was selected instead of a json.

answered Mar 4 at 22:16

Источник

Postman – один из самых популярных инструментов в области тестирования API. Он предоставляет широкий функционал, который позволяет настраивать запросы и контролировать получаемые ответы, а также проверять работу различных HTTP-методов, кодов состояния HTTP, кукисов и других важных аспектов. Однако, иногда встречаются ошибки, которые могут сбить с толку начинающих разработчиков. Один из самых распространенных видов ошибок – это «400 Bad Request». В данной статье мы рассмотрим, что такое данная ошибка, и как ее можно избежать.

Итак, что же такое «400 Bad Request»? Эта ошибка возникает, когда клиент отправляет запрос на сервер, который сервер не в состоянии обработать. В основном, ошибка 400 связана с тем, что передаваемые параметры не соответствуют требованиям сервера. Есть несколько причин возникновения этой ошибки, которые мы рассмотрим подробно ниже.

Неправильная структура JSON-документа

JSON-документ является форматом передачи данных, который используется в RESTful API. Неправильная структура этого документа может привести к ошибке «400 Bad Request». Например, если вы используете POST-запрос для отправки данных на сервер, но вами была отправлена неправильная структура JSON-документа, то сервер не сможет получить и обработать эти данные. В таких случаях, вам необходимо внимательно проверить структуру JSON-документа, чтобы убедиться, что он соответствует требованиям сервера.

Неправильный формат параметров

Если вы отправляете параметры в виде строки или числа, а сервер ожидает массив или объект, то вы получите ошибку «400 Bad Request». Например, если ваш сервер ожидает массив значений для параметра «ids», а вы отправляете его в виде строки, то сервер не сможет обработать этот запрос. В этом случае необходимо внимательно прочитать документацию вашего API и убедиться, что параметры, которые вы отправляете, соответствуют его требованиям.

Отсутствие обязательных данных

Некоторые API требуют определенных данных для выполнения запроса. Если вы не передали какие-то из этих данных, то сервер не сможет выполнить запрос. Например, если ваш API требует передачи авторизационных данных для запроса, то если вы их не передали, вы получите ошибку «400 Bad Request». В данном случае, вам следует убедиться, что вы передаете все необходимые параметры в запросе.

Ограничения на количество запросов

Некоторые API устанавливают ограничения на количество запросов, которые могут быть выполнены в течение определенного периода времени. Если вы отправляете запросы слишком быстро или превышаете установленные лимиты, то сервер может вернуть ошибку «400 Bad Request». В этом случае вам следует выяснить ограничения, установленные API, и привести количество ваших запросов в соответствие с ними.

В заключение, ошибки «400 Bad Request» в Postman могут возникать по многим причинам, таким как неправильный формат JSON-документа, отсутствие обязательных данных, использование неправильного типа параметров или превышение установленных лимитов запросов. Если вы столкнулись с этой ошибкой, а вы не знаете, как ее решить, следует внимательно прочитать документацию вашего API или связаться с его разработчиками. Также, вы можете использовать средства Postman для тестирования и отладки API-запросов, чтобы убедиться, что они корректно работают и исправно выполняют все требования сервера.

Источник

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

Go to ‘…’
Click on ‘….’
Scroll down to ‘….’
See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem. Please make sure the screenshot does not contain any sensitive information such as API keys or access tokens.

App information (please complete the following information):

App Type [e.g. Chrome App, Native App]
Postman Version [e.g. 6.0.1]
OS: [e.g. macOS High Sierra 10.13.2]

Additional context
Add any other context about the problem here.

@MuraliKrishna4550 You are going to have to give more information than this.
Can you please give us more details? Console Logs would be helpful so we can get an idea of what may be happening.

I am having the same problem.

Any POST request to any service running on any port on localhost never hits the service. It immediately errors out with a 400 Bad Request. I have included as much information as is relevant to the problem, the same request made of a valid hostname elsewhere works without issue.

MacOS 10.15.5
Postman 7.28.0 (Native App)

I recently updated Postman on a reboot and ever since I have experienced this problem, I have no issues reaching valid hostnames, it is just when I attempt to hit localhost that it nearly immediately gives a 400 and I do not see the request hit the locally running service that is being developed.

@gintohewoo The request does reach your locally running service that’s why it’s returning a 404 response.
Can you share what’s the request URL like? or, share steps that we can use to reproduce this issue locally?

Did you disable the Host request header? I see it’s missing from the attached console screenshot.

I am not sure how to disable the HOST request header.

I believe the host is missing because this request is going to localhost. I do see the host header entry when I hit the services running at a valid hostname, so perhaps this is the issue.

@gintohewoo Host header is attached to every request sent unless it’s disabled explicitly. Refer to the following screenshot and check if the Host field is disabled/unchecked.

Everything looks as it should on my end.

I have simply rolled back to an earlier version and things appear to be working now. Thank you for your assistance but I had to get this deployed by end of week this week, sorry I could not be of more help.

@hostaur Note that this setting is deprecated and will be removed in the future.

Can you share what’s the issue you are facing and got the need of turning this OFF?

I’m facing the same issue in Version 9.14.0 after the update. Where can I get the previous version of postman?

where is the problem reply as sson as possible urgent

Enable all headers. Then it works.

Источник

Problem Description:

Here’s the API info:

Request

Endpoint: {loginUrl}
Data to submit: an email and a password
POST /login HTTP/1.1
Host: {baseUrl}
Accept: application/json
Content-Type: application/json
Content-Length: 68

{
    "email": "{email}",
    "password": "{password}"
}

And in response, I should get an encrypted token in form of JSON, instead I’m getting this error.

Here are the postman screenshots:

Postman_01

Postman_02

Am I missing something?

Solution – 1

From the lack of details it’s difficult to offer a specific answer but I can offer something that you can try – The Request data you posted in the question looks like you should be adding:

{
    "email": "{email}",
    "password": "{password}"
}

Solution – 2

I also faced the same issue and i updated my postman header with the below image. And issue solved.
enter image description here

Solution – 3

The solution for me was also adding the "Content-Length" and "Host" headers in Postman.

I see some others have questioned the need for the "Content-Length" header, but in my case, the minimum three needed were "Content-Type", "Content-Length", and "Host" or it would always fail.

Solution – 4

I faced a similar issue. it got resolved when i called my placeholder as a tuple.

Источник

I have a very basic webApi built/running (pretty much template app, nothing more) in order to follow a training video. The GET and DELETE calls work fine, PUT and POST give a 400 error. Admittedly very new to all this so I’m looking for some basic direction as to how to troubleshoot. Pertinent screen shots follow, I’d be glad to provide others as requested. Thanks in advance.

asked Jan 28, 2019 at 21:10

you are trying to make POST request which needs string value in its body.

Step to the Body section of the Postman Request, select form-data after that add value as parameterName and This is test string as parameter value

answered Jan 28, 2019 at 21:14

I know this very old thread but may help someone so posting my answer.
try updating your method attribute[HttpPost(«New»)] and call it as http:localhost//api/new.

answered May 22, 2020 at 7:04

Mine is a development env on .net core.

This drove me nuts and lost 5 hours, all preventing post requests from either the browser calls or from Postman.

The following three changes helped me in 3 different scenarios.

First I disabled the https and made it only http. Commented out sslPort and removed ‘s’ from https.

Next I felt xsrf/csrf token are causing issues, so I disabled Anti Forgery token as follows. As you can see I applied the IgnoreAntiforgeryToken attribute at the controller level, but you may also apply at the action method level as needed. The token is sent anyway, but you can ask .net core to ignore it, for that route.