<div dir="ltr">Hi Karel,<div><br></div><div>I tested OpenShift as well (with CURL), which lead me to create this JIRA:</div><div><a href="https://issues.jboss.org/browse/AGPUSH-240">https://issues.jboss.org/browse/AGPUSH-240</a><br>
</div><div><br></div><div>Right now -> nothing; but some ideas in the above ticket</div><div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Aug 9, 2013 at 10:16 AM, Karel Piwko <span dir="ltr"><<a href="mailto:kpiwko@redhat.com" target="_blank">kpiwko@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi All,<br>
<br>
during testing OpenShift cartridge for Unified Push Server, I've realized that<br>
if cartridge is idle, a request wakes it up and returns HTTP 302, so the<br>
original requests is not processed. The subsequent requests is processed fine,<br>
as expected.<br>
<br>
I'm wondering whether we should make this transparent to use client users or<br>
they would need to tread this on their own.<br>
<br>
Your thoughts?<br>
<br>
Karel<br>
_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br>Matthias Wessendorf <br><br>blog: <a href="http://matthiaswessendorf.wordpress.com/" target="_blank">http://matthiaswessendorf.wordpress.com/</a><br>sessions: <a href="http://www.slideshare.net/mwessendorf" target="_blank">http://www.slideshare.net/mwessendorf</a><br>
twitter: <a href="http://twitter.com/mwessendorf" target="_blank">http://twitter.com/mwessendorf</a>
</div>