Details
-
Feature Request
-
Resolution: Done
-
Critical
-
None
-
None
-
None
-
None
Description
When the OpenShift instance is IDLE and submitting a HTTP POST against the server wakes up the instance, but the actual push messages are not delivered.
Instead the OS service returns 302.
curl -u "43f622b8-cb2c-43ec-9c85-6634628056c1":"masterSecret" -v -H "Accept: application/json" -H "Content-type: application/json" -X POST -d '{"key":"value","alert":"HELLO!","sound":"default"}' http://schema-pushee.rhcloud.com/ag-push/rest/sender/broadcast * About to connect() to schema-pushee.rhcloud.com port 80 (#0) * Trying 184.73.8.137... * connected * Connected to schema-pushee.rhcloud.com (184.73.8.137) port 80 (#0) * Server auth using Basic with user '43f622b8-cb2c-43ec-9c85-6634628056c1' > POST /ag-push/rest/sender/broadcast HTTP/1.1 > Authorization: Basic NDNmNjIyYjgtY2IyYy00M2VjLTljODUtNjYzNDYyODA1NmMxOmVlM2IyNjUxLWU5NmMtNGJhMy1iOTRiLWNlYWE3MTYzZTkyOA== > User-Agent: curl/7.24.0 (x86_64-apple-darwin12.0) libcurl/7.24.0 OpenSSL/0.9.8r zlib/1.2.5 > Host: schema-pushee.rhcloud.com > Accept: application/json > Content-type: application/json > Content-Length: 50 > * upload completely sent off: 50 out of 50 bytes < HTTP/1.1 302 Found < Date: Mon, 05 Aug 2013 05:54:06 GMT < Server: Apache/2.2.15 (Red Hat) < Vary: Host < X-Powered-By: PHP/5.3.3 < Location: http://schema-pushee.rhcloud.com/ag-push/rest/sender/broadcast < Connection: close < Content-Length: 0 < Content-Type: text/html < * Closing connection #0 pluto:~ matzew$
We need to decide what to do with that, and how the client(s) should react on this