CLOSE THIS: This has to do with self signed HTTPS cert. Tested with a good SSL and all works fine.
--- original text----
I am not sure what is going on AGOL side but when loading up a koop map (webmap viewer) it makes a call back to AGOL for server side parsing of the koop layer definition file
ex. https://myOrg.maps.arcgis.com/sharing/proxy?https://100.14.60.227:12004/koop/arcgis/rest/services/koop/htrack-locations/FeatureServer/0?f=json
And only on that request does it 500. All the rest of the requests goto koop directly and work fine. I am not sure if that is critical or not. It seems to be some sort of feature detection server side. Oddly enough it seems like that only affects the rendering of the data if that call comes back instantaneous. If its is slowed down enough that the layer queries come back at roughly the same time things render properly. If I find anything I will update this ticket.
I am not sure this is relevant to the project but I thought I would throw it out there.
CLOSE THIS: This has to do with self signed HTTPS cert. Tested with a good SSL and all works fine.
--- original text----
I am not sure what is going on AGOL side but when loading up a koop map (webmap viewer) it makes a call back to AGOL for server side parsing of the koop layer definition file ex. https://myOrg.maps.arcgis.com/sharing/proxy?https://100.14.60.227:12004/koop/arcgis/rest/services/koop/htrack-locations/FeatureServer/0?f=json And only on that request does it 500. All the rest of the requests goto koop directly and work fine. I am not sure if that is critical or not. It seems to be some sort of feature detection server side. Oddly enough it seems like that only affects the rendering of the data if that call comes back instantaneous. If its is slowed down enough that the layer queries come back at roughly the same time things render properly. If I find anything I will update this ticket.
I am not sure this is relevant to the project but I thought I would throw it out there.