In `http get` utility, headers are not working as expected

[emailstorbala]

In `http get` utility, headers are not working as expected

[emailstorbala]

@NotTheDr01ds Thank you for the http get -ef command information.
Without the authorisation headers, I was getting an output something like below:

With the auth headers, the original error starts appearing. I tried without 'Content-Type', 'Accept', with them and mixed. In all cases, I am getting the same error × MIME type unknown: application/hal+json;. Seems the http get command is not respecting our inputs in this case.

[NotTheDr01ds]

I may be wrong, but shouldn't that be Accept instead of Content-Type? curl sends a default Accept, which may explain why it's working with curl but not http get.

See this Stack Overflow answer for some more detail, including the suggestion of adding -v to the curl command to get more info.

[emailstorbala]

@NotTheDr01ds Thank you for the information.
Seems 'Accept' header and 'Content-Type' headers are for different purposes and the same is explained in the below post.
https://stackoverflow.com/questions/35722586/http-headers-accept-and-content-type-in-a-rest-context

In my case, I need to set the 'Content-Type' header only in my request to emphasise that I send a json body (mostly used in put and post.) . For GET request, this parameter is not relevant, I guess. I use nevertheless :)

[NotTheDr01ds]

Agreed - that's what made me think Content-Type was out of place in this GET example ;-)

I would suggest comparing the output of curl -v to that of Nu's http get -ef. I'm hoping the problem (and hopefully the solution) will be apparent there.

[devurandom]

I run into a similar problem. Making a request with HTTPie and bearer token succeeds, while making the same request with the same token using Nushell fails with an authentication error.

Is there a way to debug output the exact HTTP request that Nushell writes to the wire? To check where exactly the two differ?