Skip to main content
Solved

_error (string): HTTP/1.1 415 Unsupported Media Type

  • June 28, 2019
  • 3 replies
  • 103 views

nag
Contributor
Forum|alt.badge.img

Hello Team,

 

When i call following url from HTTPCaller getting error code:415 what could be the reason?

 

Following is the url:-

https://identity.trimble.com/token?username=XXXXXXXXX%40nisource.com&password=XXXXXXXX%21&grant_type=password&scope=openid&tenantDomain=trimble.com

 

Thanks...

Nagendra

Best answer by nielsgerrits

Maybe you need to keep the questions in one topic :-)

The response comes from the API, not from the HTTPCaller.

You probably need to add a Content-Type header in the request. Documentation for CURL says application/x-www-form-urlencoded.

What version FME do you use? I had some url encoding issues of parameters in earlier versions.

Did you had any success getting a token by doing a POST request in Postman?

This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

3 replies

nielsgerrits
VIP
Forum|alt.badge.img+61
  • Best Answer
  • June 28, 2019

Maybe you need to keep the questions in one topic :-)

The response comes from the API, not from the HTTPCaller.

You probably need to add a Content-Type header in the request. Documentation for CURL says application/x-www-form-urlencoded.

What version FME do you use? I had some url encoding issues of parameters in earlier versions.

Did you had any success getting a token by doing a POST request in Postman?


nag
Contributor
Forum|alt.badge.img
  • Author
  • Contributor
  • July 5, 2019

Maybe you need to keep the questions in one topic :-)

The response comes from the API, not from the HTTPCaller.

You probably need to add a Content-Type header in the request. Documentation for CURL says application/x-www-form-urlencoded.

What version FME do you use? I had some url encoding issues of parameters in earlier versions.

Did you had any success getting a token by doing a POST request in Postman?

I was using FME(R) 2015.1.1.0 (20150715 - Build 15515 - WIN64) version, Issue has been resolved by using the content_type as JSON (application/json) in the body. Earlier it was plain text. Thanks...


nielsgerrits
VIP
Forum|alt.badge.img+61

I was using FME(R) 2015.1.1.0 (20150715 - Build 15515 - WIN64) version, Issue has been resolved by using the content_type as JSON (application/json) in the body. Earlier it was plain text. Thanks...

Great! Could you share a workspace with a working HTTPCaller, without your credentials?