Zebra Browser Print Application CORS Access-Control-Allow-Headers do not include 'request-id' and 'traceparent'

M Mike Van Vugt 6 days 23 hours ago
242 0 0

We are attempting to use the Zebra Browser Print application's APIs through a PWA. The PWA is written using NodeJS and React.

When attempting to fetch the /default endpoint of the Zebra Browser Print application, the CORS request is rejected due to the CORS preflight Access-Control-Request-Headers including 'request-id' and 'traceparent' (which we are not explicitly setting). Due to the nature of the framework we are using, I do not believe there is a way to exclude these headers, and the architecture of our solution is not friendly enough for custom proxy or middleware.

Is there any way to include those headers on the Access-Control-Allowed-Headers preflight response from the Zebra Browser Print application, perhaps via configuration, or would it require an application update from Zebra? The Access-Control-Allow-Headers on the preflight response from the Zebra Browser Print application currently only include 'origin' and 'content-type'.

Is there another solution to this issue?

Any feedback would be appreciated!

CONTACT
Can’t find what you’re looking for?