Re: [aerogear-dev] How should unified push clients handle HTTP 302?

Hi All, during testing OpenShift cartridge for Unified Push Server, I've realized that if cartridge is idle, a request wakes it up and returns HTTP 302, so the original requests is not processed. The subsequent requests is processed fine, as expected. I'm wondering whether we should make this transparent to use client users or they would need to tread this on their own. Your thoughts? Karel _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev