Custom headers on uSync Complete API Calls

[NikRimington]

Hey @KevinJump I'm not sure if this is something that already happens or anything, but I was wondering. Does uSync (more specifically uSync Complete) add any custom headers to it's API call's when it's calling a different server so the requests can be identified?

I have some tooling that blocks requests but allows them through if they have a specific auth code in the query string. I added it to a pair of sites that use uSync Complete and they stopped being able to talk (obviously).

The sites are on Azure, so I white listed the Azure IP's in the tooling, but there are alot of IP's.

I am looking to modify the tool to allow it to also check for a "header" to handle API requests or the like, and was hoping that uSync already had a custom header I could check for.

This would also be useful in some cloudflare situations or other situations where sites are behind restricted access tooling.

If this is not possible currently, is it a feature that could potentially be added in the future? And could the "additional header" maybe be configurable via config?

[KevinJump]

Hi @NikRimington

yes, you can add custom request headers and user agent string values in the config.

https://docs.jumoo.co.uk/usync/complete/guides/syncPublisher/publishConfig/config#appsettingsjson-config-file

I think the docs might be off a bit. request headers are a dictionary. e.g

"RequestHeaders": {
   "header one": "custom value",
   "header two": "custom value two"
}