-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Proxy configuration under js 3.22 #10
Comments
Nothing should be different than it was at 3.21. Which version of the app proxy are you using? |
On the server side? Server is 10.22 - but I'd have to check with others for the version of proxy if that is what you are looking for. |
Kelly - Application proxy is 1.1.0. |
I ran some tests and its working for me. Are you getting any error messages? |
We ran the application through an app proxy running 1.1.2 and we are still experiencing the issue. We were able to replicate the issue on another application by changing the reference from JS 3.21 to 3.22, using both versions of the proxy we had running. This may be something specific to our instance and we have a developer who's going to open a ticket directly with you all. He's speculating there may be a change in the API related to CORS. We are getting some errors in the browser console related to preflight requests not passing access control checks that are leading him in this direction. |
Kelly,
We were unsuccessful in configuring proxy to secure map services with the version referencing the 3.22 api. When we rolled JavaScript library back to version 3.21, things worked as they have with some of the other application templates. I was unable to locate the 3.22 documentation to see if the urLUtils (urlPrefix and proxyURL) are available or referenced differently, but thought it best to mention this to you.
Tim
The text was updated successfully, but these errors were encountered: