You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I add "cors: true" to the sampleRequest in the demo, the {{jwt.token}} is not replaced with the actual token when hitting the server. Is there additional changes I have to make or is this expected behavior?
Many thanks,
Rob
The text was updated successfully, but these errors were encountered:
Hi Rob,
This is expected behaviour. Adding cors: true means you aren't able to use secure settings for that request. CORS requests are made directly from the browser to the cross-origin destination without using our secure proxy. The secure proxy is required to interpolate the value of a secure setting. If you want to interpolate values into CORS requests, they need to be normal (non-secure) settings.
Hi there,
If I add "cors: true" to the sampleRequest in the demo, the {{jwt.token}} is not replaced with the actual token when hitting the server. Is there additional changes I have to make or is this expected behavior?
Many thanks,
Rob
The text was updated successfully, but these errors were encountered: