go-spatial
When adding an http source on https://fresco.gosptail.org an incorrect error message is displayed
The issue is around protocol mismatch and loading HTTP from an HTTPS domain. The error message indicates the source could not be found. It would be better to indicate to the user that the protocol is the error. Maybe you can sniff for the error and adjust the message accordingly?
The same happens if a request is made to a tilejson resource without CORS enabled.
@pnorman Was this due to the tile server not including Access-Control-Allow-Origin headers? I've had trouble sniffing the errors registered on the client and isolating this issue to present a suitable error message. If I can gather some details from you, I can take another crack at it.
I'm not sure if it was the tile server not including it or if it was the tilejson server not including it. I added it to both and it fixed the problem.
The reason I added it to this issue is this issue and the CORS issue are both cases of browser policies blocking the loading of some content and it showing up as source could not be found
@pnorman got it. Thanks for contributing to this issue and I'll try to isolate the CORS error cases so I can present a better error message to the user. Side note: I'm getting ready to release a new, upgraded version of Fresco. Would you be interested in trying it out?