Getting Data In

Receiving '400 Bad Request' when posting data through REST Client. Is there a way to track the detailed description of the error through Splunk logs?

prem07it50
Engager

Receiving '400 Bad Request' when posting data through REST Client. Is there a way to track the detailed description of the error through Splunk logs? If so which log file would help us?

0 Karma
1 Solution

vasanthmss
Motivator

Hi

A 400 means that the request was malformed. In other words, the data stream sent by the client to the server didn't follow the rules

You should check the rest body and the response.

You can check the internal logs of the server.

Thanks
V

V

View solution in original post

vasanthmss
Motivator

Hi

A 400 means that the request was malformed. In other words, the data stream sent by the client to the server didn't follow the rules

You should check the rest body and the response.

You can check the internal logs of the server.

Thanks
V

V
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Turn Cisco Telemetry Into Action with Cisco Data Fabric, powered by the Splunk ...

The surge in machine data is already hitting enterprise budgets, and the agentic era will only intensify it. ...

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...