RSConnect, Plumber and User-Agent - "An exception occurred."

We have built some lovely APIs using plumber and deployed on Connect. Internally all work great, however one third party is having issues and we suspect its due to them not supplying User-Agent in their headers.

Does anyone know if User-Agent is a mandatory required header for calls?


1 Like

As plumber is concerned, user-agent header does not matter. I do not know for Connect.

1 Like

Could you be more specific about what "having issues" means?

For both local and 3rd party calls to the Connect API, we get "An exception occurred." when User-Agent removed.

Do you use the headers within your api?

Yes, we collate all the headers in entrypoint for logging purposes.

Try your API without this logging piece of code to see if it might be your culprit maybe?


gonna do that now, thanks! didnt even think of this!

We have hard coded the user agent in our logs where not present in the request , which has indeed solved the problem! thanks so much for your help.

1 Like

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.

If you have a query related to it or one of the replies, start a new topic and refer back with a link.