RESTDebugger fails where Postman succeeds

[dcroghan 0]

Hello,

 

I am able to prepare a Postman request that produces an expected result, which is a token.  When I attempt to use the same URL/URI, Authorization parameters, Headers, Body in RESTDebugger, I receive a 400 Bad Request error.

I am trying to determine what is different between how the 2 tools are preparing their respect requests.

Since, both tools are on the same server, firewall should not be a factor.  The Error 400 indicates to me that the request is making it to the API service.  

The request should be sending with Content-Type of "application/x-www-form-urlencoded".  I cannot verify that this format is being sent.  The request requires 3 elements in a "Body" structure that I have entered into the "Custom body" edit box.  Since the format is "application/x-www-form-urlencoded", I have entered the 3 required body elements as key1=value1&key2=value2&key3=value3.   I have tried a multitude of scenarios without success.

The service requires Basic authentication, and I have provided the Username and Password. 

 

Is there a way for RESTDebugger to display or log the request that is being sent to the server?  

 

Thanks for any help or advice.

 

Dan

Edited Wednesday at 04:06 AM by dcroghan
typo

[ertank 30]

Hello, if I need to see raw request and response, I am using Telerik Fiddler Classic (and not the Fiddler Everywhere). It might work for you. There is also Wireshark and it may provide even more detail on your needs.

[Rollo62 589]

Not that it solves your RestDebugger but, but there is also a nice tool Bruno, which might help to dig deeper.
https://www.usebruno.com/

[Dave Nottage 622]

5 minutes ago, Rollo62 said:

there is also a nice tool Bruno

I had been working on a tool of my own (Slumber) but this looks like it will do pretty much everything I visioned. Thanks!

[Rollo62 589]

17 minutes ago, Dave Nottage said:

I had been working on a tool of my own (Slumber) but this looks like it will do pretty much everything I visioned. Thanks!

Have seen it, but never checked it out before.
Its on my ToDo list now 

[Lars Fosdal 1866]

28 minutes ago, Rollo62 said:

Not that it solves your RestDebugger but, but there is also a nice tool Bruno, which might help to dig deeper.
https://www.usebruno.com/

Bruno looks quite interesting! And, it's open source!

[Lars Fosdal 1866]

I've used https://www.charlesproxy.com/ with success for seing exactly what is sent/received in a REST API.

You can also inject it into a https connection as it acts as a proxy.

[dcroghan 0]

Thank you ALL for the responses.  I will give them a try and provide updates.

[dcroghan 0]

Installed Bruno and first attempt worked perfectly.  

What I wonder is (outside of using something like Wireshark) is there a way to see the request that RESTDebugger is sending? 

 

 Since I know is works with other REST tools, it must be something in how RESTDebugger is preparing or sending the request.

 

Does RESTDebugger properly prepare the BODY element?  I have tried both the populating the Custom Body memo box and adding individual BODY type Parameters without success.

[Rollo62 589]

2 hours ago, dcroghan said:

What I wonder is (outside of using something like Wireshark) is there a way to see the request that RESTDebugger is sending? 

I was curious how far you can get with the newer System.Net.HttpClient, System.Net.HttpClientComponent, System.Net.URLClient.

It seems quite limited, perhaps the good old Indy might have more tricks up its sleeve.

TNetHTTPClient TRESTClient and friends are not so verbose in regards of internal stream data.

Perhaps a combination of both can get more insights about the underlying data streams?

 

T526_RestDebug_002.zip

Edited Wednesday at 05:50 PM by Rollo62

[dcroghan 0]

Thank you.  Let me give that a try