Forum Discussion
Custom connector returns empty header
Dear community, I'm currently trying to get a custom connector working due to an API returning information in the header of a response that is required to fetch all the data. Initially, the f...
Hi Anonymous ,
I think you may refer to blog as below to have a try.
- Click "New Policy"
- Name your policy
- Select "Set HTTP header"
- Select the Operations (Actions) that require this header
- Header name: "content-type"
- Header Value: "application/x-www-form-urlencoded"
- Action if header exists: "override"
- Run policy on: "Request"
Best Regards,
Rico Zhou
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hey Rico,
I did this, but this didn't make a difference. As I indicated earlier, it did work before and after deleting a method that I put before the original contents method I worked again. Also, I checked the raw data coming in and I could see that even when the connector didn't show me the headers. They actually were there, so there is a very odd bug at play here...
kind regards,
Vincent