Skip to content
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

Do not allow OGC layers from servers with no CORS/JSONP (?) #365

Open
gioman opened this issue May 16, 2017 · 3 comments
Open

Do not allow OGC layers from servers with no CORS/JSONP (?) #365

gioman opened this issue May 16, 2017 · 3 comments
Labels

Comments

@gioman
Copy link

gioman commented May 16, 2017

Adding a OGC layer, a WMS from example, for a server with no CORS/JSONP will make WAB send a message like

"There was an error loading tiles."

then on webapp preview the layer with load to fail with

There was an error loading tiles.

wouldn't be better to "ban" altogether the OGC layers that are from services/servers that are not supported?

@gioman gioman added the bug label May 16, 2017
@bartvde
Copy link
Contributor

bartvde commented May 22, 2017

Probably yes, I agree

Alternatively we could not set crossOrigin: 'anonymous' in those cases

@gioman
Copy link
Author

gioman commented May 23, 2017

@bartvde whatever can result in less confusion for users. I personally think strange (as user) I cannot add a whataver WMS Mapserver layer, but is that is not possible then block them.

@SrNetoChan
Copy link
Contributor

Meanwhile, I will document this limitation in the troubleshooting section.

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

No branches or pull requests

3 participants