Calling custom HTTPS Connector, import POST changes to GET

Integrator.io
1

Hi,

I'm testing a custom RESTFUL API server with the HTTPS connector and I'm running into a weird issue.

I set my IMPORT step to POST to my custom API connector... if I Preview the IMPORT step, it does state "POST" as the method... but when I finally "Send" it to actually run a test, it seems to be running a GET instead of a POST... and I'm at loss... Can anyone shed some light?

Here are my import parameters with a Preview already formed:

image
image1836×988 93.5 KB

But when I actually hit Send, it seems to be making a GET call, not a POST call -- my server confirms that by not issuing any life signal on my post function, just on my get function:

image
image957×397 17.9 KB

image

Any insights on why this is happening?

Thanks in advance,

2

@marceloborges I ran into this same issue in the past. It was explained to me to prepend a forward slash to the relative URI, so update "csv" to "/csv". This worked for me, YMMV.

3

Hi @bryancarroll thank you so much for the feedback, but it doesn't seem this solution worked for me. I tried all different combinations of forward slashes:

csv
/csv
csv/
/csv/

and I even tried to remove the API name from the relative URI and add directly on the Import step:

json2CSV/csv
/json2CSV/csv
json2CSV/csv/
/json2CSV/csv/

And none of these worked either. It still kept on switching to GET :frowning:

4

Sorry, @marceloborges. I tried to find the post/case I created surrounding this. It was a bug discovered in a Tuesday office hours and there was a lot of back and forth and eventually a ticket created to track. The bug was fixed, but I was still having the issue of the POST getting rewritten as a GET request. I was eventually told that I needed to prepend the forward-slash to the relative URI to get it to work correctly, and that behavior was by design. I wish I could provide more detail but, unfortunately, I can't find the communications I had with Celigo on this. So sorry, I wish I could be of more help.

5

If you enable debug logs on the export in the top right, is there a 3XX response where it's then redirecting? Or a Location header being returned on the first call?