Skip to content
This repository has been archived by the owner on Apr 26, 2023. It is now read-only.

Add Intellisense in proxy.config #486

Merged
merged 6 commits into from
May 15, 2018
Merged

Conversation

nicogis
Copy link
Contributor

@nicogis nicogis commented May 14, 2018

Add Intellisense VS in proxy.config

@bsvensson bsvensson merged commit e73edd1 into Esri:master May 15, 2018
@bsvensson
Copy link
Member

Thanks @nicogis for helping improve the resource-proxy!

@bsvensson
Copy link
Member

FYI: it looks like after this commit, users of the DotNet proxy, need to update their proxy.config as in the commit 3f00000#diff-619e6e6c6786d5cebe866bfb1ab4492f

If you update your resource-proxy for DotNet, but keep your old proxy.config as is, your proxy will probably break saying [InvalidOperationException: <ProxyConfig xmlns=''> was not expected.]

Basically, the DotNet proxy is now "stricter", and you just have to change from
<ProxyConfig allowedReferers="*" mustMatch="false">
in your proxy.config to
<ProxyConfig allowedReferers="*" mustMatch="false" xmlns="proxy.xsd">

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants