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

[Matthias Wessendorf]

Hi Karel,

I tested OpenShift as well (with CURL), which lead me to create this JIRA:
https://issues.jboss.org/browse/AGPUSH-240

Right now -> nothing; but some ideas in the above ticket



On Fri, Aug 9, 2013 at 10:16 AM, Karel Piwko <kpiwko at redhat.com> wrote:

> 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 at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20130809/e2a6caca/attachment.html